II07664: MSGIEC161I 052-084 RC52 RSN84 DIAGNOSTIC TIPS VSAMINFO : ENQUEUE

APAR status

• Closed as canceled.

Error description

• LAST UPDATE: 06/17/99
  r240 r310 r311 r330 r332 r110 r1b0 r1c0 r1d0 r1g0 r1h0 r1j0
  OPEN message IEC161I 052-084 is a common informational message.
  Most often it simply means that another job already has the
  dataset open when this job is trying to open it.  As it usually
  indicates a scheduling problem rather than a system problem,
  the purpose of this APAR is to provide information on how to
  determine what jobs are in contention for the same dataset.
  .
  VSAM OPEN processing determines this condition by checking the
  GRS data.  Depending on the shareoptions (SHR) of the dataset,
  and the attributes of the OPEN, VSAM will enqueue against major
  name SYSVSAM with a minor name of the dataset name/catalog name
  plus other information.  Thus, GRS is the mechanism OPEN pro-
  cessing uses to insure serialization of the OPEN process itself
  as well as the shareoptions of the file.
  When VSAM issues an ENQUEUE for a SYSVSAM resource, VSAM will
  add an ENQRNIND indicator to the wanted resource name:
       ENQRNIND = B = BUSY
       ENQRNIND = I = INPUT
       ENQRNIND = N = Non RLS Open
       ENQRNIND = O = OUTPUT
       ENQRNIND = P = Non RLS Open for output
       ENQRNIND = R = RESERVE
       ENQRNIND = S = Sphere
       ENQRNIND = C = CLOSE
       ENQRNIND = R = RLS Read
       ENQRNIND = W = RLS Write
  The ENQ for BUSY will be held throughout the period of the
  initial operation being performed, i.e., OPEN, EOV, CLOSE,
  TCLOSE or CHECKPOINT RESTART.  When the operation is complete
  or is failed, then, the 'B' resource will be dequeued.  Example:
       ENQ DATASET/CAT/B  (OPEN)  EXCLUSIVE
       ENQ DATASET/CAT/O
       DEQ DATASET/CAT/B
         (process data)
       ENQ DATASET/CAT/B  (CLOSE) EXCLUSIVE
       DEQ DATASET/CAT/O
       DEQ DATASET/CAT/B
  .
  The first place to look to determine which job is enqueued on
  the dataset is GRS data.  You can view this data with the
  DISPLAY GRS command or thru a monitor program.  Look at both
  the global and local queues under the major name of SYSVSAM for
  the dataset that is getting the OPEN failure.  Unfortunately,
  the GRS data is transient and may well change before you can
  find the job that was responsible for the message, but, do try
  the GRS command.  Issue this GRS command from all systems that
  can share the DASD:  D GRS,RES=(SYSVSAM,*)
  .
  NOTE:  If you are using IPCS to view GRSDATA remember that
  SYSVSAM will be there twice, once for Local System Resources
  and a second time for Global Systems Resources.
  .
  The next place to look is the console log.  You may be able to
  determine if there were any backups/copies/dumps being taken at
  the time or even if there were unexpected batch jobs running at
  the time.
  .
  Another place to look for information is the SMF type 62 (SMF62)
  and SMF64 records.  This will show what jobs were accessing
  the dataset at the time of the error.  This also may not be
  conclusive since some access of the dataset will not produce
  SMF records (i.e., Media Manager, DB2, DF/DSS).
  .
  The programmers response as noted by msgIEC161I RC52  notes:
  (1)  Ensure the availability of the resource by means of JCL DD
  statements.  This means, check your JCL and ensure that you have
  requested the proper disposition, i.e., DISP=SHR
  (2)  Use the Access Methods Services command ALTER, to reset
  the Update Inhibit indicator in the data set's catalog record
  then, rerun the job.  This means, run LISTC against the failed
  cluster, check for an attribute of INH-UPDATE.  If found ON,
  then this dataset is in READONLY mode and will fail an OPEN
  for UPDATE request.  Use the AMS command 'ALTER UNINHIBIT'
  to place the file in READ/WRITE mode, then, rerun the job.
  EXAMPLE:  Cluster  DFP1.JIMONE.KSDS is getting OPEN errors, the
  cluster is on a D/T3390 with a volume serial number of 339000:
  ----------------------------------------------------------------
  //SYSIN DD *
       PRINT  INDATASET(SYS1.VVDS.V339000) DUMP
       ALTER  DFP1.JIMONE.KSDS.DATA  UNINHIBIT
       ALTER  DFP1.JIMONE.KSDS.INDEX UNINHIBIT
       VERIFY DATASET(DFP1.JIMONE.KSDS)
       LISTC  ENT(DFP1.JIMONE.KSDS) ALL
  /*
  ----------------------------------------------------------------
  In a VSAM catalog, INHIBIT UPDATE bit is in the BCS DINC record.
  In an ICF catalog, INHIBIT UPDATE bit is in the VVDS VVR record.
  .
  If you are  NOT  able to determine what job is the cause of the
  IEC161I message, open a problem record with the Support Center
  and include your RMID of IDA0192B.  You will be given a SLIP to
  capture a dump (which includes the GRSQ data) at the time the
  message is issued.
  The SLIP will be set in CSECT IDA0192B of load module IDA0192A
  upon entry to a procedure named, PROBDT2B ...  IBM will need to
  know the PTF level of IDA0192B in order to resolve the offset
  of xxx in the SLIP.  The user will need an AMBLIST of IDA0192A,
  IDA0192B is an offset into load module IDA0192A and PROBDT2B is
  an offset into IDA0192B.  xxx is the sum of these 2 offsets.
  The value of xxx and values specified in the SLIP DATA parms
  may change with different releases and maintenance levels of
  CSECT IDA0192B.  Be sure to check with IBM Support Personnel
  to ensure an accurate SLIP for your level.
  .
  ----------------------------------------------------------------
  SLIP SET,IF,A=SYNCSVCD,L=(IDA0192A,xxx),DATA=(13R?+F8,EQ,34),
       SDATA=(ALLNUC,CSA,GRSQ,LPA,LSQA,RGN,SQA,SUM,TRT),END
  ----------------------------------------------------------------
  Example with IDA0192B at UW29246:
  SLIP SET,IF,A=SYNCSVCD,L=(IDA0192A,xxx),DATA=(13R?+8B8,EQ,34),
       SDATA=(ALLNUC,CSA,GRSQ,LPA,LSQA,RGN,SQA,SUM,TRT),END
  where xxx = offset of IDA0192B into IDA0192A plus x'2A02'.
  .
  Example with IDA0192B at UW48057:
  SLIP SET,IF,A=SYNCSVCD,L=(IDA0192A,2A00),DATA=(13R?+8F8,EQ,34),
       SDATA=(ALLNUC,CSA,GRSQ,LPA,LSQA,RGN,SQA,SUM,TRT),END
  .
  Example with IDA0192B at UW50162:
  SLIP SET,IF,A=SYNCSVCD,L=(IDA0192A,xxx),DATA=(13R?+8F4,EQ,34),
       SDATA=(ALLNUC,CSA,GRSQ,LPA,LSQA,RGN,SQA,SUM,TRT),END
  where xxx = offset of IDA0192B into IDA0192A plus x'28FE'.
  .
  Example with IDA0192B at UW58997:
  SLIP SET,IF,A=SYNCSVCD,L=(IDA0192A,xxx),DATA=(13R?+8E8,EQ,34),
       SDATA=(ALLNUC,CSA,GRSQ,LPA,LSQA,RGN,SQA,SUM,TRT),END
  where xxx = offset of IDA0192B into IDA0192A plus x'28E2'.
  .
  Example with IDA0192B at UW79979:
  SLIP SET,IF,A=SYNCSVCD,L=(IDA0192A,xxx),DATA=(13R?+944,EQ,34),
       SDATA=(ALLNUC,CSA,GRSQ,LPA,LSQA,RGN,SQA,SUM,TRT),END
  where xxx = offset of IDA0192B into IDA0192A plus x'2B2E'.
  
  The trigger for the SLIP is GR13 which will be the address of
  IDA0192B's MWA (module work area).  MWA+nn = MWAPCODE for a
  return code = x'34' (RC52).  Use this info with IPCS  GRSTRACE.
  Also insure that the System trace is set at a value that is
  high enough to trace the SVC19, thru error SVC56, request flow.
  USE your MVS trace command:  TRACE ST,999K
  ----------------------------------------------------------------
  .
  ADDITIONAL KEYWORDS:
  MSGIEC161I RC52 RC052 RC84 RC084 RSN84 rsn084 RSN61
  MSGIDC3351I OPEN RC168
  MSGIDC3300I ERROR OPENING dsname
  MSGDSNJ100I ERROR OPENING BSDS ERROR STATUS 08A8
  VSAM     566528451 566528452 5695DF106
  CATALOG  566528418 5695DF105
  r1d0
  .
  VSAMINFO : ENQUEUE  LOCKOUT (see OY67291 for related GRS info)
  SVC19 (0A13) OPEN   SVC56 (0A38) ENQUEUE   SVC48 (0A30) DEQUEUE
  NOTE: Beware of products like IBM's DFDSS.  It is NOT uncommon
        for a DSS DASD maintenance operation to be running on one
        member of a sharing complex while normal production oper-
        ations are also accessing the DASD.  If DSS acquires an
        exclusive enqueue on the wanted data set, the production
        system could encounter the 052-84 error.
        Check the RETAIN database for APARs associated with the
        related product in regard to ENQUEUE DEQUEUE.
        (DFDSS = 5695DF175   DSS = 566532701)
  .
  MSGIDC3009I RC48 RC56 IDC3009I VVRA1IUP
  Reset processing of a Reusable data set encountered the inhibit
  bit = ON.  Use same procedure as msgIEC161I RC56.  Use IDCAMS
  ALTER UNINHIBIT
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• MVS/ESA PLANNING: GRS              GC28162103
  DFSMS/MVS R1B0  : USING DATA SETS  SC26492201
  DB2INFO 5740XYR00 DB2
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels