That's obvious if You think before You write.  An outrageous requirement. 

 
Regards, 
Thomas Berg 
_________________________________________ 
Thomas Berg   Specialist   A M   SWEDBANK 



> -----Ursprungligt meddelande-----
> Från: IBM Mainframe Discussion List [mailto:[email protected]] För Mike
> Schwab
> Skickat: den 27 oktober 2011 14:28
> Till: [email protected]
> Ämne: Re: Which manual for ECA* messages ?
> 
> The reason code came from the EMC product.  You will have to look up
> that code in the EMC Manual.
> 
> >  11/10/27 10:07:04 ECA1004E RECALL OF P950OBA.A.CNTL FAILED.  RETURN
> CODE: 4764.
> >  ARC1001I P950OBA.A.CNTL  RECALL FAILED, RC=0099, REAS=4764
> 
> On Thu, Oct 27, 2011 at 6:16 AM, Thomas Berg <[email protected]>
> wrote:
> > As we now have an "all IBM" policy it didn't occur to me that it could
> be a non-ibm message.
> > I have looked for the ARC1001I message with the result as below...
> >
> > The whole error message (some line cutted at the end):
> >
> > ARC1020I DFSMSHSM IS RECALLING FROM DASD DSN=P950OBA.A.CNTL, YOU MAY
> CONTINUE T
> > SSION BY PRESSING THE ATTENTION KEY
> >  11/10/27 10:07:04 ECA1004E RECALL OF P950OBA.A.CNTL FAILED.  RETURN
> CODE: 4764.
> >  ARC1010I USER REQUEST FOR A MIGRATED DATA SET FAILED.
> >  ARC1001I P950OBA.A.CNTL  RECALL FAILED, RC=0099, REAS=4764
> >  ARC1199I ERROR DURING RECALL/RECOVERY
> >  ***
> >
> > Whats more irritating is that when looking at ARC1001I, the reasoncode
> is not found in the manual.
> > (z/OS V1R1.0 MVS System Messages, Vol 2 (ARC-ASA) - which is where the
> link from z/OS V1R13.0 DFSMShsm Diagnosis is pointing to.)
> > That is, they say:
> >
> > 2.671 ARC1001I
> >
> >   ARC1001I {dsname | VOL=volser | command} operation FAILED, RC=retcode
> >          REAS=reascode
> >
> > Explanation: A DFSMShsm request has failed. The following describes the
> message variables:
> >
> >    * dsname indicates the name of the data set.
> >    * volser indicates the volume serial number.
> >    * command indicates the command and its associated command
> parameters.
> >    * operation indicates the requested operation.
> >    * retcode indicates the return code.
> >    * reascode indicates the reason code.
> >
> > A following related message provides you with further information about
> the failure. The two digits of the message number specified as nn,
> indicate the retcode. The related message number also indicates the
> DFSMShsm function processing when the failure has occurred, as shown on
> the following table.
> >
> >
> >
> >  Table 2. Return Code Identifier
> >                           Function                          Message
> Group
> >                    Recovery/Recall
> ARC11nns
> >                   Space Management
> ARC12nns
> >                             Backup
> ARC13nns
> >          Aggregate Backup/Recovery
> ARC6nnns
> >
> >
> > For example, if the related message is ARC1131I:
> >
> >    * ARC1131I indicates that the recovery/recall function has failed.
> The nn is 31 which is the retcode. See Table 3 in topic 2.1266 for the
> meaning of retcode 31 or refer to message ARC1131I for expanded
> information.
> >
> >
> >
> > - So I look at ARC1199, where I find:
> >
> > 2.787 ARC1199I
> >
> >   ARC1199I ERROR DURING RECALL/RECOVERY
> >
> > Explanation: An error was detected while DFSMShsm was performing a
> recall or recovery operation. The return and reason code are given in
> message ARC1001I. The possible values for the reason code are:
> >
> > Reascode Meaning
> >
> > 4
> >    A data set was requested to be reblocked and the accumulated record
> length was greater than the DCBLRECL.
> >
> > 8
> >    A direct access data set was targeted to a volume with a smaller
> track capacity than the volume where the data set originally resided.
> >
> > 12
> >    The DFSMShsm CDS record that describes the data set indicated a
> source volume device type that is not supported by DFSMShsm.
> >
> >
> >
> > - Non sequitur AFAICS.  I the look in "ARC Return Codes and Reason
> Codes"  where I finally find:
> >
> > " 99             VBS data set RECOVER/RECALL attempted to incompatible
> device."
> >
> > - Which is somewhat unlikely for a JCL dataset.
> >
> > - REAS=4764 is nowhere to find
> >
> >
> >
> > Regards,
> > Thomas Berg
> > _________________________________________
> > Thomas Berg   Specialist   A M   SWEDBANK
> 
> --
> Mike A Schwab, Springfield IL USA
> Where do Forest Rangers go to get away from it all?
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: GET IBM-MAIN INFO
> Search the archives at http://bama.ua.edu/archives/ibm-main.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to