DFHSM ARCLOGx ARCLOGy must be on the same volume.
Hello, We recently 'switched' on the ARCLOGx and ARCLOGy functionality of DFHSM. All working perfectly well. However, apparently it is somewhat required to have both output datasets residing on the same volume. (else messages like ARC0022I may appear at swaplog-time). This is all documented well, however I do not understand why this requirement is there. Does anyone have an idea why DFHSM is unable to handle a rename when both output datasets do not reside on the same volume? Many thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM ARCLOGx ARCLOGy must be on the same volume.
Since you have not had an answer, I will give it a try. When DFHSM was developed it was probably the only way that IBM could ENSURE that the two files would be available. Not sure what would happen if one of them went missing. So it is probably something hard coded within DFHSM itself. Is it still needed in today's environment? I am not sure. Maybe someone else will if this answer seems right. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ron K. Sent: Friday, September 06, 2013 2:58 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: DFHSM ARCLOGx ARCLOGy must be on the same volume. Hello, We recently 'switched' on the ARCLOGx and ARCLOGy functionality of DFHSM. All working perfectly well. However, apparently it is somewhat required to have both output datasets residing on the same volume. (else messages like ARC0022I may appear at swaplog-time). This is all documented well, however I do not understand why this requirement is there. Does anyone have an idea why DFHSM is unable to handle a rename when both output datasets do not reside on the same volume? Many thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM ARCLOGx ARCLOGy must be on the same volume.
If it is an error reported by the RENAME service, there should also be an IEC614I message with the details as described in chapter 6 of the DFSMSdfp Diagnosis manual. Are your log datasets SMS managed? :: -Original Message- :: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On :: Behalf Of Ron K. :: Sent: Friday, September 06, 2013 2:58 AM :: To: IBM-MAIN@LISTSERV.UA.EDU :: Subject: DFHSM ARCLOGx ARCLOGy must be on the same volume. :: :: Hello, :: :: We recently 'switched' on the ARCLOGx and ARCLOGy functionality of DFHSM. :: All working perfectly well. However, apparently it is somewhat required :: to have both output datasets residing on the same volume. (else messages :: like ARC0022I may appear at swaplog-time). This is all documented well, :: however I do not understand why this requirement is there. :: :: Does anyone have an idea why DFHSM is unable to handle a rename when :: both output datasets do not reside on the same volume? :: :: Many thanks. :: :: -- :: For IBM-MAIN subscribe / signoff / archive access instructions, :: send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
