RE: Error deleting data area... -- MIDRANGE-L





The same program does get submitted again about an hour later during our
nightly processing stuff.  That time, the program worked fine, and the data
area was deleted successfully.  Go figure....

I wonder what will happen tonight.  Guess I'll have to dial in to find
out... :(

Thanks all for the suggestions...
Todd



                                                                           
             "Jeff Rogers"                                                 
             <jeff.rogers@trgc                                             
             orp.com>                                                   To 
             Sent by:                  "'Midrange Systems Technical        
             midrange-l-bounce         Discussion'"                        
             s@xxxxxxxxxxxx            <midrange-l@xxxxxxxxxxxx>           
                                                                        cc 
                                                                           
             11/09/2005 03:47                                      Subject 
             PM                        RE: Error deleting data area...     
                                                                           
                                                                           
             Please respond to                                             
             Midrange Systems                                              
                 Technical                                                 
                Discussion                                                 
             <midrange-l@midra                                             
                 nge.com>                                                  
                                                                           
                                                                           




You've probably tried this, but wrkobjlck may show you what has a lock on
the data area.

Jeff

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
todd.sabella@xxxxxxxxxxxxx
Sent: Wednesday, November 09, 2005 11:26 AM
To: Midrange Systems Technical Discussion
Subject: Error deleting data area...






For the second time in a few days, we have received this error when trying
to delete a data area within a batch job.

The data area is created in the submitting program.  Then a new program is
submitted.  The submitted program checks for the data area, retrieves its
value, and is supposed to delete the data area.  It has worked fine for a
number of years.

If the object was locked by something else, I would have expected to see
CPF2114 (Cannot allocate object WHICH01 in RTAM type DTAARA. ). But instead
we're getting CPFA030 (Object already in use) which mentions threads.

Along with a program dump, the system printed the job information.  There
was only one thread for the job...

 5722SS1 V5R2M0 020719                      Work with Job
                                               Threads
                           Total        Aux         Run
 Thread   Status      CPU         I/O       Priority
00000004  RUN            .066         57       50


Anyone have any ideas ??

Thanks,
Todd

A snippet of the job log....

 Message . . . . :    12800 - CHKOBJ OBJ(RTAM/WHICH01) OBJTYPE(*DTAARA)
    05/11/09  00:40:55.174600  QCADRV       QSYS        0391     CIRT0200
R
 Message . . . . :    13300 - RTVDTAARA DTAARA(RTAM/WHICH01) RTNVAR(&WHICH)
    05/11/09  00:40:55.183232  QCADRV       QSYS        0391     CIRT0200
R
 Message . . . . :    13400 - DLTDTAARA DTAARA(RTAM/WHICH01)
   05/11/09  00:40:55.206864  QP0QCHK      QSYS        *STMT    CIRT0200
R
 From module . . . . . . . . :   QP0QCHK
 From procedure  . . . . . . :   qp0qchk__FP15chk_parms_block
 Statement . . . . . . . . . :   642
 Message . . . . :   Object already in use.
 Cause . . . . . :   Cannot allocate object for reason code 1. 1 -- Object
   WHICH01 of type *DTAARA in library RTAM is in use by another thread. 2
--
   Member WHICH01 in file , library RTAM is in use by another thread.
Recovery
   . . . :   Wait until the object is no longer in use and try the request
again.
   05/11/09  00:40:55.252880  QCLXERR      QSYS        00DA     QCLXERR
Q
 Message . . . . :   CPFA030 received by CIRT0200 at 13400. (C D I R)
 Cause . . . . . :   Control language (CL) program CIRT0200 in library RTAM
   detected an error at statement number 13400. Message text for CPFA030
is:
   Object already in use. Recovery  . . . :   This inquiry message can be
   avoided by changing the program. Monitor for the error (MONMSG command)
and
   perform error recovery within the program. To continue, choose a reply
   value. Possible choices for replying to message . . . . . . . . . . . .
. .
   . :   C -- Cancel the CL program. D -- Dump the CL program variables and
   cancel the CL program. I -- Ignore the failing command. R -- Try the
failin
   command again.
    05/11/09  00:40:55.268208  QMHSNINQ     QSYS        0CDD     QCLXERR
Q
 Message . . . . :   D
0   05/11/09  00:40:55.233824  QMHUNMSG                 *N       QCMD
Q
 Message . . . . :   Function check. CPFA030 unmonitored by CIRT0200 at
   statement 13400, instruction X'006F'.