Re: LTO 5 in 3584 tape library and z/OS
I found a list of supported device types here http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2g610/D.0?ACTION=MATCHESREQUEST=magnetic+tape+devicesTYPE=EXACTNSHELF=all13be9DT=20050713135418CASE=searchTopic=TOPICsearchText=TEXTsearchIndex=INDEXrank=ScrollTOP=FIRSTHIT#FIRSTHIT Strictly speaking, that is all that is supported. However, any device that can successfully emulate one of those device types is supported. Hence, all the latest IBM tape drives emulate 3590-1 and the system can even tell you what they are - TS1120 etc. Virtual tape has to emulate also one of these devices - most are emulating 3490, and to be correctly reported as a virtual library some OAM support is needed to recognise them. Any non-IBM tape can only be reported by z/OS as an IBM 'equivalent' - whatever the manufacturer chose to report to z/OS. Tape management systems attempt to navigate their way through all this to tell you what is really going on out there. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: LTO 5 in 3584 tape library and z/OS
W dniu 2013-08-29 11:53, Mike Wood pisze: I found a list of supported device types here http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2g610/D.0?ACTION=MATCHESREQUEST=magnetic+tape+devicesTYPE=EXACTNSHELF=all13be9DT=20050713135418CASE=searchTopic=TOPICsearchText=TEXTsearchIndex=INDEXrank=ScrollTOP=FIRSTHIT#FIRSTHIT Strictly speaking, that is all that is supported. However, any device that can successfully emulate one of those device types is supported. Hence, all the latest IBM tape drives emulate 3590-1 and the system can even tell you what they are - TS1120 etc. Virtual tape has to emulate also one of these devices - most are emulating 3490, and to be correctly reported as a virtual library some OAM support is needed to recognise them. Any non-IBM tape can only be reported by z/OS as an IBM 'equivalent' - whatever the manufacturer chose to report to z/OS. Tape management systems attempt to navigate their way through all this to tell you what is really going on out there. Strictly speaking it is possible to add non-IBM UIM and then another device type definition. IMHO it's not populr, but it used to be used just for tape drives. To repeat/complement Mike's words: IBM stopped creating new HCD/IOCP device types at 3590-1 level (created for first MAGSTAR drive). All newer tape drives use 3590-1 as a hardware definition. But this is only part of the truth: although the HCD definition for 3590-B, 3590-H or 3592-E06 are exactly the same, there are siginificant differences between thos drive types and the differences are *recognized* by various software components, like DS QT command or DFHSM. DFHSM will shout if you order him to use a set of inconsistent devices , for example unit 3590-1 when you have various devices f this dev type defined. In that case you have to use esoteric name covering only devices of given hardware model. My €0.02 -- Radoslaw Skorupka Lodz, Poland -- Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2013 r. kapitał zakładowy BRE Banku SA (w całości wpłacony) wynosi 168.555.904 złotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
DFDSS problem
Hello friends! I am trying to restore some files that were backed up with DFDSS some time ago, and I am having a problem with the results. If I let DFDSS allocate the file, I get an output file with a Blocksize of zero, although all the space amounts are fine. I then tried to use OUTDD(), and if I specify Blksize/Lrecl/Recfm or if I don't, I still get a Blocksize zero. If I specify the blocksize, I get this warning (but the file is Blksize 0): ADR398W (001)-TDUNL(02), DATA SET xxx.xxx.xxx BLOCKSIZE OF 04096 IS INCORRECT. LARGEST BLOCKSIZE IS 4096. Does anyone have any idea what could be happening, or how I can override the DCB that DFDSS wants to use? I no longer have access to the backup job, so can't see the output. Here is my input: RESTORE DATASET(INCLUDE(xxx.xxx.xxx)) INDD(BKP) - OUTDD(FILE420) BYPASSACS(**) REPLACEU -- Thank you and best regards, *Billy Ashton* -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS problem
Sometimes when I run into strange issues with DFDSS, I will bring the dataset back as a new name and then browse the file after it is restored. If you are getting blksize 0 then maybe the file on backup is empty. I would try creating a new file:filename.recv (I use RECV as a suffix so I know it is a recovered file.) and then browse it. It maybe that your file has no data. In which case I would just allocate it rather than trying to restore it. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bill Ashton Sent: Thursday, August 29, 2013 5:43 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: DFDSS problem Hello friends! I am trying to restore some files that were backed up with DFDSS some time ago, and I am having a problem with the results. If I let DFDSS allocate the file, I get an output file with a Blocksize of zero, although all the space amounts are fine. I then tried to use OUTDD(), and if I specify Blksize/Lrecl/Recfm or if I don't, I still get a Blocksize zero. If I specify the blocksize, I get this warning (but the file is Blksize 0): ADR398W (001)-TDUNL(02), DATA SET xxx.xxx.xxx BLOCKSIZE OF 04096 IS INCORRECT. LARGEST BLOCKSIZE IS 4096. Does anyone have any idea what could be happening, or how I can override the DCB that DFDSS wants to use? I no longer have access to the backup job, so can't see the output. Here is my input: RESTORE DATASET(INCLUDE(xxx.xxx.xxx)) INDD(BKP) - OUTDD(FILE420) BYPASSACS(**) REPLACEU -- Thank you and best regards, *Billy Ashton* -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS problem
Hi Lizette, and thanks for your note. I have done the restore with a new name with no difference. I have also dumped the backup with IDCAMS, and I can see the data, which looks like the right format - there is a bunch of data as I expected. Unfortunately, the original file is no longer available, which is why I am trying to get this backup to work. I have to say that I am not the happiest guy at the moment. Billy On Thu, Aug 29, 2013 at 8:52 AM, Lizette Koehler stars...@mindspring.comwrote: Sometimes when I run into strange issues with DFDSS, I will bring the dataset back as a new name and then browse the file after it is restored. If you are getting blksize 0 then maybe the file on backup is empty. I would try creating a new file:filename.recv (I use RECV as a suffix so I know it is a recovered file.) and then browse it. It maybe that your file has no data. In which case I would just allocate it rather than trying to restore it. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bill Ashton Sent: Thursday, August 29, 2013 5:43 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: DFDSS problem Hello friends! I am trying to restore some files that were backed up with DFDSS some time ago, and I am having a problem with the results. If I let DFDSS allocate the file, I get an output file with a Blocksize of zero, although all the space amounts are fine. I then tried to use OUTDD(), and if I specify Blksize/Lrecl/Recfm or if I don't, I still get a Blocksize zero. If I specify the blocksize, I get this warning (but the file is Blksize 0): ADR398W (001)-TDUNL(02), DATA SET xxx.xxx.xxx BLOCKSIZE OF 04096 IS INCORRECT. LARGEST BLOCKSIZE IS 4096. Does anyone have any idea what could be happening, or how I can override the DCB that DFDSS wants to use? I no longer have access to the backup job, so can't see the output. Here is my input: RESTORE DATASET(INCLUDE(xxx.xxx.xxx)) INDD(BKP) - OUTDD(FILE420) BYPASSACS(**) REPLACEU -- Thank you and best regards, *Billy Ashton* -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Thank you and best regards, *Billy Ashton* -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
CBT tape files directly onto z/OS.
I suppose most of us get things off of the CBTTape.org web site by using a desktop browser to go to the web site and save as to our PC. Then unzip the file on our PC. Then ftp upload the XMIT file up to z/OS. I've gotten tired of this. So I found a way to cheat. In case anyone is curious, this is how I do it interactively. It requires installing the ported tools version of curl and Java installed. 1) go to the CBTtape.org site to determine the URL of the CBTtape file you want. E.g. cbttape.org/ftp/updates/CBT897.zip 2) get to a z/OS UNIX shell and enter the following UNIX commands cd some-subdirectory curl -B http://cbttape.org/ftp/updates/CBT987.zip jar xf CBT987.zip ls -ltr #to find name of extracted file cp -B -W seqparms='space=(cyl,(1,1)),recfm=fb,lrecl=80,blksize=3120' FILE897.XMI exit 3) do the normal RECEIVE INDATASET(FILE897.XMI) to restore the PDS. I don't know if the above will be of any use to anybody other than myself. -- As of next week, passwords will be entered in Morse code. Maranatha! John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS problem
If you could provide a little more detail. Is the file being restored VSAM, SEQ, PDS, PDSE? What will be the file attributes when restored? When was the file last on DASD? Was there a backup then? What was the results? Any warning messages? When was the file backed up? What jobstream. Did you review the last backup to see if there were errors for this file? Do you have DFHSM? If so, is there an HSM Backup of the file? HLIST DSN(filename) BCDS will let you know If there is a DFHSM Backup then HRECOV filename should work Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bill Ashton Sent: Thursday, August 29, 2013 6:10 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFDSS problem Hi Lizette, and thanks for your note. I have done the restore with a new name with no difference. I have also dumped the backup with IDCAMS, and I can see the data, which looks like the right format - there is a bunch of data as I expected. Unfortunately, the original file is no longer available, which is why I am trying to get this backup to work. I have to say that I am not the happiest guy at the moment. Billy On Thu, Aug 29, 2013 at 8:52 AM, Lizette Koehler stars...@mindspring.comwrote: Sometimes when I run into strange issues with DFDSS, I will bring the dataset back as a new name and then browse the file after it is restored. If you are getting blksize 0 then maybe the file on backup is empty. I would try creating a new file:filename.recv (I use RECV as a suffix so I know it is a recovered file.) and then browse it. It maybe that your file has no data. In which case I would just allocate it rather than trying to restore it. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bill Ashton Sent: Thursday, August 29, 2013 5:43 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: DFDSS problem Hello friends! I am trying to restore some files that were backed up with DFDSS some time ago, and I am having a problem with the results. If I let DFDSS allocate the file, I get an output file with a Blocksize of zero, although all the space amounts are fine. I then tried to use OUTDD(), and if I specify Blksize/Lrecl/Recfm or if I don't, I still get a Blocksize zero. If I specify the blocksize, I get this warning (but the file is Blksize 0): ADR398W (001)-TDUNL(02), DATA SET xxx.xxx.xxx BLOCKSIZE OF 04096 IS INCORRECT. LARGEST BLOCKSIZE IS 4096. Does anyone have any idea what could be happening, or how I can override the DCB that DFDSS wants to use? I no longer have access to the backup job, so can't see the output. Here is my input: RESTORE DATASET(INCLUDE(xxx.xxx.xxx)) INDD(BKP) - OUTDD(FILE420) BYPASSACS(**) REPLACEU -- Thank you and best regards, *Billy Ashton* -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Thank you and best regards, *Billy Ashton* -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS problem
Bill Ashton wrote: Here is my input: RESTORE DATASET(INCLUDE(xxx.xxx.xxx)) INDD(BKP) - OUTDD(FILE420) BYPASSACS(**) REPLACEU When running the RESTORE, what is the attributes of the backup? Logical or Physical? AFAIK, there is a difference. Why BYPASSACS(**)? Why REPLACEU if those datasets are not there at all? You could just use INCLUDE(**) with PARM='TYPRUN=NORUN' just to see what all were backup in the first place. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS problem
Sorry about the clutter in the commandsBYPASSACS is there as I was trying to ignore the groups it was originally using and restore the file to non-SMS volumes. The REPLACEU was an attempt (unsuccessful, obviously) to pre-allocate the files and to restore into them (with OUTDD), and then to just try and restore and replace the pre-allocated files. I have tried lots of different ways, with no success. On Thu, Aug 29, 2013 at 9:29 AM, Elardus Engelbrecht elardus.engelbre...@sita.co.za wrote: Bill Ashton wrote: Here is my input: RESTORE DATASET(INCLUDE(xxx.xxx.xxx)) INDD(BKP) - OUTDD(FILE420) BYPASSACS(**) REPLACEU When running the RESTORE, what is the attributes of the backup? Logical or Physical? AFAIK, there is a difference. Why BYPASSACS(**)? Why REPLACEU if those datasets are not there at all? You could just use INCLUDE(**) with PARM='TYPRUN=NORUN' just to see what all were backup in the first place. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Thank you and best regards, *Billy Ashton* -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS problem
I cannot guarantee this will work but two things to try. 1) Preallocate the new file with your attributes. Restore to that file. DFDSS may honor your file with the blksize you want. 2) Restore the file even if it gets a BLKSIZE of 0. Then use IEBGENER to do the following //SYSUT1 DD * /* yes a null entry //SYSUT2 DD DISP=OLD,DSN=yourfilename,BLKSIZE=4096,LRECL=... When IEBGENER opens and closes the file, it could use your BLKSIZE in the JCL to override what was restored. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bill Ashton Sent: Thursday, August 29, 2013 6:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFDSS problem I'm sorry for leaving all this out...my brain is a bit weary. The file is a PS file, F/4096, and is one of 3 files in the backup (the other two have the same results). It was quite a while ago on disk (when it was backed up), and there is no output to review, but I am assuming the backup worked fine, since the data in the backup file looks good/ We have no HSM backups or archives - only this DFDSS backup - to work with. On Thu, Aug 29, 2013 at 9:20 AM, Lizette Koehler stars...@mindspring.comwrote: If you could provide a little more detail. Is the file being restored VSAM, SEQ, PDS, PDSE? What will be the file attributes when restored? When was the file last on DASD? Was there a backup then? What was the results? Any warning messages? When was the file backed up? What jobstream. Did you review the last backup to see if there were errors for this file? Do you have DFHSM? If so, is there an HSM Backup of the file? HLIST DSN(filename) BCDS will let you know If there is a DFHSM Backup then HRECOV filename should work Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bill Ashton Sent: Thursday, August 29, 2013 6:10 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFDSS problem Hi Lizette, and thanks for your note. I have done the restore with a new name with no difference. I have also dumped the backup with IDCAMS, and I can see the data, which looks like the right format - there is a bunch of data as I expected. Unfortunately, the original file is no longer available, which is why I am trying to get this backup to work. I have to say that I am not the happiest guy at the moment. Billy On Thu, Aug 29, 2013 at 8:52 AM, Lizette Koehler stars...@mindspring.comwrote: Sometimes when I run into strange issues with DFDSS, I will bring the dataset back as a new name and then browse the file after it is restored. If you are getting blksize 0 then maybe the file on backup is empty. I would try creating a new file:filename.recv (I use RECV as a suffix so I know it is a recovered file.) and then browse it. It maybe that your file has no data. In which case I would just allocate it rather than trying to restore it. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bill Ashton Sent: Thursday, August 29, 2013 5:43 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: DFDSS problem Hello friends! I am trying to restore some files that were backed up with DFDSS some time ago, and I am having a problem with the results. If I let DFDSS allocate the file, I get an output file with a Blocksize of zero, although all the space amounts are fine. I then tried to use OUTDD(), and if I specify Blksize/Lrecl/Recfm or if I don't, I still get a Blocksize zero. If I specify the blocksize, I get this warning (but the file is Blksize 0): ADR398W (001)-TDUNL(02), DATA SET xxx.xxx.xxx BLOCKSIZE OF 04096 IS INCORRECT. LARGEST BLOCKSIZE IS 4096. Does anyone have any idea what could be happening, or how I can override the DCB that DFDSS wants to use? I no longer have access to the backup job, so can't see the output. Here is my input: RESTORE DATASET(INCLUDE(xxx.xxx.xxx)) INDD(BKP) - OUTDD(FILE420) BYPASSACS(**) REPLACEU -- Thank you and best regards, *Billy Ashton* -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Thank you and best regards, *Billy Ashton* -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Thank you and best regards, *Billy Ashton* -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: CBT tape files directly onto z/OS.
On Thu, 29 Aug 2013 08:10:51 -0500, John McKown wrote: 1) go to the CBTtape.org site to determine the URL of the CBTtape file you want. E.g. cbttape.org/ftp/updates/CBT897.zip 2) get to a z/OS UNIX shell and enter the following UNIX commands cd some-subdirectory curl -B http://cbttape.org/ftp/updates/CBT987.zip (We need to specify a proxy. And for some sites, --location) FTP works as well. Our proxy is even more Byzantine for FTP. I did this before we had Ported Tools. jar xf CBT987.zip ls -ltr #to find name of extracted file cp -B -W seqparms='space=(cyl,(1,1)),recfm=fb,lrecl=80,blksize=3120' FILE897.XMI exit 3) do the normal RECEIVE INDATASET(FILE897.XMI) to restore the PDS. Or, BPXWDYN( 'alloc path(...)...' ) RECEIVE INFILE ... I can do all this in a batch job. Need to stack the response to RECEIVE prompt. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: EMC DLM Data Domain and z/OS
W dniu 2013-08-29 15:15, Lizette Koehler pisze: [...] You can respond to my private email : starsoul at mindspring dot com I cannot. IP xxx.aa.bbb.ccc is blocked by EarthLink. Go to earthlink.net/block for details. -- Radoslaw Skorupka Lodz, Poland -- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. Wedug stanu na dzie 01.01.2013 r. kapita zakadowy BRE Banku SA (w caoci wpacony) wynosi 168.555.904 zotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS problem
Sorry, my mind was misfiring a neuron. That should have been DISP=MOD on the SYSUT2 DD statement for Gener. Sorry about that. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler Sent: Thursday, August 29, 2013 6:37 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFDSS problem I cannot guarantee this will work but two things to try. 1) Preallocate the new file with your attributes. Restore to that file. DFDSS may honor your file with the blksize you want. 2) Restore the file even if it gets a BLKSIZE of 0. Then use IEBGENER to do the following //SYSUT1 DD * /* yes a null entry //SYSUT2 DD DISP=OLD,DSN=yourfilename,BLKSIZE=4096,LRECL=... When IEBGENER opens and closes the file, it could use your BLKSIZE in the JCL to override what was restored. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bill Ashton Sent: Thursday, August 29, 2013 6:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFDSS problem I'm sorry for leaving all this out...my brain is a bit weary. The file is a PS file, F/4096, and is one of 3 files in the backup (the other two have the same results). It was quite a while ago on disk (when it was backed up), and there is no output to review, but I am assuming the backup worked fine, since the data in the backup file looks good/ We have no HSM backups or archives - only this DFDSS backup - to work with. On Thu, Aug 29, 2013 at 9:20 AM, Lizette Koehler stars...@mindspring.comwrote: If you could provide a little more detail. Is the file being restored VSAM, SEQ, PDS, PDSE? What will be the file attributes when restored? When was the file last on DASD? Was there a backup then? What was the results? Any warning messages? When was the file backed up? What jobstream. Did you review the last backup to see if there were errors for this file? Do you have DFHSM? If so, is there an HSM Backup of the file? HLIST DSN(filename) BCDS will let you know If there is a DFHSM Backup then HRECOV filename should work Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bill Ashton Sent: Thursday, August 29, 2013 6:10 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFDSS problem Hi Lizette, and thanks for your note. I have done the restore with a new name with no difference. I have also dumped the backup with IDCAMS, and I can see the data, which looks like the right format - there is a bunch of data as I expected. Unfortunately, the original file is no longer available, which is why I am trying to get this backup to work. I have to say that I am not the happiest guy at the moment. Billy On Thu, Aug 29, 2013 at 8:52 AM, Lizette Koehler stars...@mindspring.comwrote: Sometimes when I run into strange issues with DFDSS, I will bring the dataset back as a new name and then browse the file after it is restored. If you are getting blksize 0 then maybe the file on backup is empty. I would try creating a new file:filename.recv (I use RECV as a suffix so I know it is a recovered file.) and then browse it. It maybe that your file has no data. In which case I would just allocate it rather than trying to restore it. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bill Ashton Sent: Thursday, August 29, 2013 5:43 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: DFDSS problem Hello friends! I am trying to restore some files that were backed up with DFDSS some time ago, and I am having a problem with the results. If I let DFDSS allocate the file, I get an output file with a Blocksize of zero, although all the space amounts are fine. I then tried to use OUTDD(), and if I specify Blksize/Lrecl/Recfm or if I don't, I still get a Blocksize zero. If I specify the blocksize, I get this warning (but the file is Blksize 0): ADR398W (001)-TDUNL(02), DATA SET xxx.xxx.xxx BLOCKSIZE OF 04096 IS INCORRECT. LARGEST BLOCKSIZE IS 4096. Does anyone have any idea what could be happening, or how I can override the DCB that DFDSS wants to use? I no longer have access to the backup job, so can't see the output. Here is my input: RESTORE DATASET(INCLUDE(xxx.xxx.xxx)) INDD(BKP) - OUTDD(FILE420) BYPASSACS(**) REPLACEU -- Thank you and best regards, *Billy Ashton* -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Thank you and best regards, *Billy Ashton* -- For IBM-MAIN subscribe / signoff / archive access instructions, send
Re: EMC DLM Data Domain and z/OS
Radoslaw Skorupka wrote: Lizette Koehler wrote: You can respond to my private email : starsoul at mindspring dot com I cannot. IP xxx.aa.bbb.ccc is blocked by EarthLink. Go to earthlink.net/block for details. Try using IBM-MAIN web page where you can compose a private reply to Lizette. You unmark out the 'To the List' and mark the 'To the Poster'. HTH! Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS problem
Lizette Koehler wrote: Sorry, my mind was misfiring a neuron. Thats a new one! Must remember it, using ALL my last neurons! ;-D Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS problem
Lizette, you are a genius, and I could hug you! Here is the Gener step - I changed the null sysut1 to avoid the conflicting DCB attributes message: //GENERUO2 EXEC PGM=IEBGENER,REGION=0M //SYSINDD DUMMY //SYSPRINT DD SYSOUT=* //SYSUT1 DD DUMMY,LRECL=4096,BLKSIZE=4096,RECFM=F //SYSUT2 DD DISP=MOD,DSN=xxx.xxx.xxx, // LRECL=4096,BLKSIZE=4096,RECFM=F Thank you so much, and thanks to you too, Elardus, for your input! On Thu, Aug 29, 2013 at 10:16 AM, Elardus Engelbrecht elardus.engelbre...@sita.co.za wrote: Lizette Koehler wrote: Sorry, my mind was misfiring a neuron. Thats a new one! Must remember it, using ALL my last neurons! ;-D Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Thank you and best regards, *Billy Ashton* -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Homegrown Healthcheck Maintenance
Having successfully written tested my first homegrown Healthcheck, I now wish to deploy it and was wondering how folks generally maintain these. Is it a step too far to install it as an SMP/E usermod? I am thinking of deploying it to SAXREXEC (using a name alphabetically after I). However it also has a message table associated with it, which I could also maintain with SMP/E, but that message table has to be pushed through the HZSMSGEN utilitity to generate assembler source, which then needs to be assembled/linked into LINKLIB? Starting to look messy! Any thoughts gratefully received. Andrew Metcalfe -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS problem
On 8/29/2013 8:37 AM, Lizette Koehler wrote: I cannot guarantee this will work but two things to try. 1) Preallocate the new file with your attributes. Restore to that file. DFDSS may honor your file with the blksize you want. 2) Restore the file even if it gets a BLKSIZE of 0. Then use IEBGENER to do the following //SYSUT1 DD * /* yes a null entry //SYSUT2 DD DISP=OLD,DSN=yourfilename,BLKSIZE=4096,LRECL=... When IEBGENER opens and closes the file, it could use your BLKSIZE in the JCL to override what was restored. I think this should be: //SYSUT2 DD DISP=(MOD,KEEP),DSN=yourfilename,BLKSIZE=4096,LRECL=... With DISP=OLD it will write an EOF at the front of the file. -- Richard -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS problem
I am happy it worked out. Have a better day. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bill Ashton Sent: Thursday, August 29, 2013 7:31 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFDSS problem Lizette, you are a genius, and I could hug you! Here is the Gener step - I changed the null sysut1 to avoid the conflicting DCB attributes message: //GENERUO2 EXEC PGM=IEBGENER,REGION=0M //SYSINDD DUMMY //SYSPRINT DD SYSOUT=* //SYSUT1 DD DUMMY,LRECL=4096,BLKSIZE=4096,RECFM=F //SYSUT2 DD DISP=MOD,DSN=xxx.xxx.xxx, // LRECL=4096,BLKSIZE=4096,RECFM=F Thank you so much, and thanks to you too, Elardus, for your input! On Thu, Aug 29, 2013 at 10:16 AM, Elardus Engelbrecht elardus.engelbre...@sita.co.za wrote: Lizette Koehler wrote: Sorry, my mind was misfiring a neuron. Thats a new one! Must remember it, using ALL my last neurons! ;-D Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Thank you and best regards, *Billy Ashton* -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS problem
I know this is obvious, but I would do a backup and restore of the file (new name) and verify it works the way it should. You should be able to do a RESTORE without the BYPASSACS and the file should be correct. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bill Ashton Sent: Thursday, August 29, 2013 7:31 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFDSS problem Lizette, you are a genius, and I could hug you! Here is the Gener step - I changed the null sysut1 to avoid the conflicting DCB attributes message: //GENERUO2 EXEC PGM=IEBGENER,REGION=0M //SYSINDD DUMMY //SYSPRINT DD SYSOUT=* //SYSUT1 DD DUMMY,LRECL=4096,BLKSIZE=4096,RECFM=F //SYSUT2 DD DISP=MOD,DSN=xxx.xxx.xxx, // LRECL=4096,BLKSIZE=4096,RECFM=F Thank you so much, and thanks to you too, Elardus, for your input! On Thu, Aug 29, 2013 at 10:16 AM, Elardus Engelbrecht elardus.engelbre...@sita.co.za wrote: Lizette Koehler wrote: Sorry, my mind was misfiring a neuron. Thats a new one! Must remember it, using ALL my last neurons! ;-D Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Thank you and best regards, *Billy Ashton* -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Share Webinar on DFSMS
In case you did not see this, Share is sponsoring the following webinar (free) An Introduction to DFSMS Date and Time: Thursday, September 5, 12:00 p.m. ET Speaker: Steve Pryor, Senior Software Designer at DTS Software, Inc. Description: Learn in detail the aspects of SMS constructs, ACM routine coding and DASD. DFSMS plays a vital role in the data center, controlling DASD datasets throughout their life cycle, from initial allocation to final expiration. The ACS routines and the SMS constructs (data class, storage class, management class, and storage group) are at the heart of system-managed storage and an understanding of their function and coding is important for any z/OS user. This session will provide an introduction to DFSMS, including a discussion of the most important aspects of each of the SMS constructs, examples of ACS routine coding, and a discussion of SMS management of tape as well as DASD. Steve Pryor is a senior software designer at DTS Software, Inc., with over 30 years of experience in the design, development, and support of z/OS storage systems. He has spoken at numerous SHARE and other industry conferences and has taught on storage topics both domestically and internationally. He currently teaches courses in Innovation Data Processing's FDRABR DASD management system and other topics. He is also a stage actor. Register today. This should be good for those not as familiar with DFSMS as you would like. http://www.share.org/p/cm/ld/fid=28 Lizette -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Homegrown Healthcheck Maintenance
I gave up on using the message tables and started having my messages all in the REXX. Since it is not too critical, I just let the rexes live in the library allocated by AXR and changed it there if necessary. Regards, Leo -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Andrew Metcalfe Sent: Thursday, August 29, 2013 10:31 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Homegrown Healthcheck Maintenance Having successfully written tested my first homegrown Healthcheck, I now wish to deploy it and was wondering how folks generally maintain these. Is it a step too far to install it as an SMP/E usermod? I am thinking of deploying it to SAXREXEC (using a name alphabetically after I). However it also has a message table associated with it, which I could also maintain with SMP/E, but that message table has to be pushed through the HZSMSGEN utilitity to generate assembler source, which then needs to be assembled/linked into LINKLIB? Starting to look messy! Any thoughts gratefully received. Andrew Metcalfe -- 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
Re: LTO 5 in 3584 tape library and z/OS
This explains why there's no support for direct I/O for z/OS hosts to LTO, but I could never figure out why you can't use them as stacked VTS tapes. What's the point of using different media, drives, and controllers, in the same library, if all I'm doing is virtual? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: LTO 5 in 3584 tape library and z/OS
W dniu 2013-08-29 17:20, Guy Eshel pisze: This explains why there's no support for direct I/O for z/OS hosts to LTO, but I could never figure out why you can't use them as stacked VTS tapes. What's the point of using different media, drives, and controllers, in the same library, if all I'm doing is virtual? You can use LTO as stacked tapes. It is IBM decision to not use those devices in their solution, but other vendors do support any storage. Luminex, Bustech (*), Interkom, Centricstor and other vendors do (did) offer such attachments. (*) Bustech is now part of EMC and due to EMC decision support only EMC disk boxes. -- Radoslaw Skorupka Lodz, Poland -- Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2013 r. kapitał zakładowy BRE Banku SA (w całości wpłacony) wynosi 168.555.904 złotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: EMC DLM Data Domain and z/OS
See below. On Thu, Aug 29, 2013 at 8:15 AM, Lizette Koehler stars...@mindspring.com wrote: We are beginning to investigate the possibility of having a DLm and Data Domain tapeless solution in our shop. We are just looking If anyone in a medium to large shop is using this, and you would like to share your observations with me, that would be great. We have about 1PB of tape storage (mostly HSM ML2 data) between my two data centers. We have 4.7T for 10,000 volumes * 50 volumes ranges. 235TB total, 61% active volumes. Make sure you activate TTL (time to live) scratch tape management (when it reclaims scratch volumes as free space). And I would like that data to be replicated to both devices. I will also have long tern retention needs for some of my data. I need to have my primary tape data in the secondary data center for DR. It would be nice to have my critical development data sent to the primary site just in-case the DR site is the one that is down. Mostly my Source Management files. We duplicate all VTapes from a DLm 960 to DLm 4080s. I don't think we have dedup installed. EMC is suggestion an DLm8000 family and Data Domain for dedup of the data for the mainframe. Some questions I might be interested in How is the performance when the data has to be rehydrated? Is there any significant impact on distances between DD + DLm for DR usage? What size transmission pipe will make it happy? Our Primary and secondary sites are about 800 miles apart. Our sites are about 200 miles apart. Our fiber falls behind during our evening batch backup window, but catches back up by 7am. It is Async, so it is not waiting for responses. We are upgrading the fiber, last link won't be in for another 18 months. Are there any concerns or issues that might be good to know up front? Any lessons learned. We did not do TTL. We ended up with some file systems with lots of little volumes, chewed up the scratch tapes, had a lot of free space, and was attracting all the writes. Be sure to implement TTL to keep the file systems balanced. Thanks for any input. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Homegrown Healthcheck Maintenance
Well, if there is a requirement to be in LINKLIB, then yes, by all means SMPE usermod. However, if it can be any library linklist accessible, then you have choices. If it were me I would find a way to use SMPE. _ Dave Jousma Assistant Vice President, Mainframe Engineering david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Andrew Metcalfe Sent: Thursday, August 29, 2013 10:31 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Homegrown Healthcheck Maintenance Having successfully written tested my first homegrown Healthcheck, I now wish to deploy it and was wondering how folks generally maintain these. Is it a step too far to install it as an SMP/E usermod? I am thinking of deploying it to SAXREXEC (using a name alphabetically after I). However it also has a message table associated with it, which I could also maintain with SMP/E, but that message table has to be pushed through the HZSMSGEN utilitity to generate assembler source, which then needs to be assembled/linked into LINKLIB? Starting to look messy! Any thoughts gratefully received. Andrew Metcalfe -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
CPACF
Is there any command that can be issued to determine if CPACF is activated and/or FC 3863 is installed? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: CPACF
No that I know of. Bit 0x40 of Byte 2 of the FLCFACL field of the PSA is documented in POP as an indicator. After that, you can use the KMC or KMD instructions to interrogate which CPACF functions are available. Kirk Wolf Dovetailed Technologies http://dovetail.com On Thu, Aug 29, 2013 at 1:34 PM, gsg gsg_...@yahoo.com wrote: Is there any command that can be issued to determine if CPACF is activated and/or FC 3863 is installed? -- 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
UNIT=SEP still alive (?)
I just found the following in some IBM same JCL (job, actually): //SYSUT1 DD UNIT=(SYSDA,SEP=(SORTLIB,SYSLMOD,SYSLIN)), // SPACE=(1000,(60,20)) Last change date is half of the 2013 (creation date is probably 2005 or so). As far as I know SEP is syntax checked and ignored for many moons, at least since first OS/390, but I vaguely remember somebody told me it was obsoleted with advent of MVS. -- Radoslaw Skorupka Lodz, Poland -- Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2013 r. kapitał zakładowy BRE Banku SA (w całości wpłacony) wynosi 168.555.904 złotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: UNIT=SEP still alive (?)
OK, what does (did) SEP= do? The only thing the JCL reference says is that you can't use it as a JCL symbol in certain types of jobs. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Thursday, August 29, 2013 3:18 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: UNIT=SEP still alive (?) I just found the following in some IBM same JCL (job, actually): //SYSUT1 DD UNIT=(SYSDA,SEP=(SORTLIB,SYSLMOD,SYSLIN)), // SPACE=(1000,(60,20)) Last change date is half of the 2013 (creation date is probably 2005 or so). As far as I know SEP is syntax checked and ignored for many moons, at least since first OS/390, but I vaguely remember somebody told me it was obsoleted with advent of MVS. -- Radoslaw Skorupka Lodz, Poland -- Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2013 r. kapitał zakładowy BRE Banku SA (w całości wpłacony) wynosi 168.555.904 złotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN The information contained in this e-mail may contain confidential and/or privileged information and is intended for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any unauthorized use, disclosure, distribution or copying of this communication is strictly prohibited and that you will be held responsible for any such unauthorized activity, including liability for any resulting damages. As appropriate, such incident(s) may also be reported to law enforcement. If you received this e-mail in error, please reply to sender and destroy or delete the message and any attachments. Thank you. NOTICE: This e-mail message, including any attachments and appended messages, is for the sole use of the intended recipients and may contain confidential and legally privileged information. If you are not the intended recipient, any review, dissemination, distribution, copying, storage or other use of all or any portion of this message is strictly prohibited. If you received this message in error, please immediately notify the sender by reply e-mail and delete this message in its entirety. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: UNIT=SEP still alive (?)
W dniu 2013-08-29 22:48, Pommier, Rex R. pisze: OK, what does (did) SEP= do? The only thing the JCL reference says is that you can't use it as a JCL symbol in certain types of jobs. See ancient (really old!) version of JCL manual. I don't have any here, but my failing memory says it was used for unit (device) separation. The example I presented says: create SYSUT1 dataset, on some disk belonging to SYSDA, but avoid using devices already used for the following datasets: SORLTIB ,etc -- Radoslaw Skorupka Lodz, Poland -- Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2013 r. kapitał zakładowy BRE Banku SA (w całości wpłacony) wynosi 168.555.904 złotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: UNIT=SEP still alive (?)
SEP= was supposed to guarantee that the data sets were placed on SEParate volumes. Likely to enhance concurrent I/O overlap. On Thu, Aug 29, 2013 at 3:48 PM, Pommier, Rex R. rex.pomm...@cnasurety.comwrote: OK, what does (did) SEP= do? The only thing the JCL reference says is that you can't use it as a JCL symbol in certain types of jobs. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Thursday, August 29, 2013 3:18 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: UNIT=SEP still alive (?) I just found the following in some IBM same JCL (job, actually): //SYSUT1 DD UNIT=(SYSDA,SEP=(SORTLIB,SYSLMOD,SYSLIN)), // SPACE=(1000,(60,20)) Last change date is half of the 2013 (creation date is probably 2005 or so). As far as I know SEP is syntax checked and ignored for many moons, at least since first OS/390, but I vaguely remember somebody told me it was obsoleted with advent of MVS. -- Radoslaw Skorupka Lodz, Poland -- Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2013 r. kapitał zakładowy BRE Banku SA (w całości wpłacony) wynosi 168.555.904 złotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN The information contained in this e-mail may contain confidential and/or privileged information and is intended for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any unauthorized use, disclosure, distribution or copying of this communication is strictly prohibited and that you will be held responsible for any such unauthorized activity, including liability for any resulting damages. As appropriate, such incident(s) may also be reported to law enforcement. If you received this e-mail in error, please reply to sender and destroy or delete the message and any attachments. Thank you. NOTICE: This e-mail message, including any attachments and appended messages, is for the sole use of the intended recipients and may contain confidential and legally privileged information. If you are not the intended recipient, any review, dissemination, distribution, copying, storage or other use of all or any portion of this message is strictly prohibited. If you received this message in error, please immediately notify the sender by reply e-mail and delete this message in its entirety. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- As of next week, passwords will be entered in Morse code. Maranatha! John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: UNIT=SEP still alive (?)
On 2013-08-29 14:56, John McKown wrote: SEP= was supposed to guarantee that the data sets were placed on SEParate volumes. Likely to enhance concurrent I/O overlap. This was probably most effective if yours was the only job running in the system at that instant. On Thu, Aug 29, 2013 at 3:48 PM, Pommier, Rex R. wrote: OK, what does (did) SEP= do? The only thing the JCL reference says is that you can't use it as a JCL symbol in certain types of jobs. Probably jobs started by operator commands, which supported an abbreviated syntax for overrides. So they removed the function but retained the restriction. A triumph of compatibility over common sense. //SYSUT1 DD UNIT=(SYSDA,SEP=(SORTLIB,SYSLMOD,SYSLIN)), -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: UNIT=SEP still alive (?)
I started as a JCL jockey in Prod Support, under MVS. It was still supported, then (pre-XA). - Ted MacNEIL eamacn...@yahoo.ca Twitter: @TedMacNEIL -Original Message- From: John McKown john.archie.mck...@gmail.com Sender: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU Date: Thu, 29 Aug 2013 15:56:49 To: IBM-MAIN@LISTSERV.UA.EDU Reply-To: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU Subject: Re: UNIT=SEP still alive (?) SEP= was supposed to guarantee that the data sets were placed on SEParate volumes. Likely to enhance concurrent I/O overlap. On Thu, Aug 29, 2013 at 3:48 PM, Pommier, Rex R. rex.pomm...@cnasurety.comwrote: OK, what does (did) SEP= do? The only thing the JCL reference says is that you can't use it as a JCL symbol in certain types of jobs. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Thursday, August 29, 2013 3:18 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: UNIT=SEP still alive (?) I just found the following in some IBM same JCL (job, actually): //SYSUT1 DD UNIT=(SYSDA,SEP=(SORTLIB,SYSLMOD,SYSLIN)), // SPACE=(1000,(60,20)) Last change date is half of the 2013 (creation date is probably 2005 or so). As far as I know SEP is syntax checked and ignored for many moons, at least since first OS/390, but I vaguely remember somebody told me it was obsoleted with advent of MVS. -- Radoslaw Skorupka Lodz, Poland -- Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2013 r. kapitał zakładowy BRE Banku SA (w całości wpłacony) wynosi 168.555.904 złotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN The information contained in this e-mail may contain confidential and/or privileged information and is intended for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any unauthorized use, disclosure, distribution or copying of this communication is strictly prohibited and that you will be held responsible for any such unauthorized activity, including liability for any resulting damages. As appropriate, such incident(s) may also be reported to law enforcement. If you received this e-mail in error, please reply to sender and destroy or delete the message and any attachments. Thank you. NOTICE: This e-mail message, including any attachments and appended messages, is for the sole use of the intended recipients and may contain confidential and legally privileged information. If you are not the intended recipient, any review, dissemination, distribution, copying, storage or other use of all or any portion of this message is strictly prohibited. If you received this message in error, please immediately notify the sender by reply e-mail and delete this message in its entirety. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- As of next week, passwords will be entered in Morse code. Maranatha! John McKown
Re: UNIT=SEP still alive (?)
Back in Ye Olde days, it allowed for specifying that a different device address be used thus improving I/O performance. On Thu, 29 Aug 2013 20:48:30 + Pommier, Rex R. rex.pomm...@cnasurety.com wrote: :OK, what does (did) SEP= do? The only thing the JCL reference says is that you can't use it as a JCL symbol in certain types of jobs. : :-Original Message- :From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. :Sent: Thursday, August 29, 2013 3:18 PM :To: IBM-MAIN@LISTSERV.UA.EDU :Subject: UNIT=SEP still alive (?) : :I just found the following in some IBM same JCL (job, actually): ://SYSUT1 DD UNIT=(SYSDA,SEP=(SORTLIB,SYSLMOD,SYSLIN)), :// SPACE=(1000,(60,20)) : :Last change date is half of the 2013 (creation date is probably 2005 or so). :As far as I know SEP is syntax checked and ignored for many moons, at least since first OS/390, but I vaguely remember somebody told me it was obsoleted with advent of MVS. : :-- :Radoslaw Skorupka :Lodz, Poland -- Binyamin Dissen bdis...@dissensoftware.com http://www.dissensoftware.com Director, Dissen Software, Bar Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: UNIT=SEP still alive (?)
It was also useful when creating a backup so that the backup was not on the same device as the original. I noticed this... JCL example z/OS V1R12.0 Metal C Programming Guide and Reference SA23-2225-03 ... //SYSUT1 DD UNIT=(SYSDA,SEP=SYSLIB),SPACE=(CYL,(10,5)),DSN=SYSUT1 Dan -Original Message- From: Binyamin Dissen Back in Ye Olde days, it allowed for specifying that a different device address be used thus improving I/O performance. On Thu, 29 Aug 2013 20:48:30 + Pommier, Rex R. Rex.Pommier wrote: :OK, what does (did) SEP= do? The only thing the JCL reference says is that you can't use it as a JCL symbol in certain types of jobs. : :-Original Message- : :I just found the following in some IBM same JCL (job, actually): ://SYSUT1 DD UNIT=(SYSDA,SEP=(SORTLIB,SYSLMOD,SYSLIN)), :// SPACE=(1000,(60,20)) : :Last change date is half of the 2013 (creation date is probably 2005 or so). :As far as I know SEP is syntax checked and ignored for many moons, at least since first OS/390, but I vaguely remember somebody told me it was obsoleted with advent of MVS. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: UNIT=SEP still alive (?)
The z/OS V1R9 MVS JCL Reference--The 12th edition of 2007 September and the oldest one I have on my workstation--describes AFF, SEP, SPLIT, and SUBALLOC as obsolete subparameters on page 5-18. John Gilmore, Ashland, MA 01721 - USA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: CPACF
Yes. Bit 17 of the result area of the STFLE (Store Facility List Extended) instruction is set to one (1) when the Message Security Assist (i.e., CPACF) is available. In addition, bit 76 is set to one (1) when the Message Security Assist Extension 3 is available, and bit 77 is set to one (1) when the Message Security Assist Extension 4 is available. You can then use the query function of each of the various CPACF-supplied instructions to determine the availability of more granular capabilities. John P. Baker -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of gsg Sent: Thursday, August 29, 2013 2:35 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: CPACF Is there any command that can be issued to determine if CPACF is activated and/or FC 3863 is installed? -- 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
Re: CPACF
Hi, Maybe not a command, but I noticed these messages when I start my TN3270 server w/SSL support. This is from a z9BC. I *think* this indicates CPACF is installed and active. System SSL: SHA-1 crypto assist is available System SSL: SHA-224 crypto assist is available System SSL: SHA-256 crypto assist is available System SSL: SHA-384 crypto assist is not available System SSL: SHA-512 crypto assist is not available System SSL: DES crypto assist is available System SSL: DES3 crypto assist is available System SSL: AES 128-bit crypto assist is available System SSL: AES 256-bit crypto assist is not available System SSL: ICSF services are not available HTH, BobL -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of gsg Sent: Thursday, August 29, 2013 12:35 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: CPACF [ External ] Is there any command that can be issued to determine if CPACF is activated and/or FC 3863 is installed? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are not the intended recipient or their designee, please notify the sender immediately by return e-mail and delete all copies. OppenheimerFunds may, at its sole discretion, monitor, review, retain and/or disclose the content of all email communications. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: UNIT=SEP still alive (?)
On 29 Aug 2013 14:33:21 -0700, in bit.listserv.ibm-main you wrote: The z/OS V1R9 MVS JCL Reference--The 12th edition of 2007 September and the oldest one I have on my workstation--describes AFF, SEP, SPLIT, and SUBALLOC as obsolete subparameters on page 5-18. I can see SEP, SPLIT and SUBALLOC being obsolete but AFF still should be useful in conserving device use for tape drives. For example SORTIN and SORTOUT many times were allocated that way. Clark Morris John Gilmore, Ashland, MA 01721 - USA -- 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
Re: UNIT=SEP still alive (?)
In 3ebf9c9d119fd847b3a096c515a018f6949e4...@surfsdvmp35.cnasurety.net, on 08/29/2013 at 08:48 PM, Pommier, Rex R. rex.pomm...@cnasurety.com said: OK, what does (did) SEP= do? Separated allocations on different devices; think of it as the opposite of AFF. -- Shmuel (Seymour J.) Metz, SysProg and JOAT Atid/2http://patriot.net/~shmuel We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: CPACF
On Thu, 29 Aug 2013 15:45:08 -0500, gsg gsg_...@yahoo.com wrote: Sorry about that. I was told that you can check to see if CPACF is active fromt he HMC console. I was asking where to find it. does anyone know of any other way? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN If you are in Single Object Operations for the CPC, and display its details, on the Instance Information page at the bottom right is the text: CP Assist for Crypto functions: Installed (this is from a z196 that has FC3863 activated). cheers Peter -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMS Notices from Jes2
If you are interested in a vendor product, we also have a product (SyzMPF/z) which will notify via eMail or SMS text when a job ENDs/ABENDs/JCL Error, etc. as well as hundreds of other console message traffic related controls and actions. It's exremely inexpensive and provides automation support beyond just sending email and text. You can get information at www.SyzygyInc.com/SyzMPFz Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: UNIT=SEP still alive (?)
At 20:48 + on 08/29/2013, Pommier, Rex R. wrote about Re: UNIT=SEP still alive (?): OK, what does (did) SEP= do? The only thing the JCL reference says is that you can't use it as a JCL symbol in certain types of jobs. Others have also answered. To expand on what they said, UNIT=SYSDA says to allocate the dataset on one of the volumes that are addressed by SYSDA. It will select all volumes which has this address and then decide on one of them using other criteria (such as if there is enough free space on the volume to meet the requested SPACE parm). SEP says to remove the volumes which have been allocated to SORTLIB, SYSLMOD, and SYSLIN from the list of SYSDA volumes and only select from the remaining volumes - ie: Treat those volumes as if they were not part of SYSDA. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Thursday, August 29, 2013 3:18 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: UNIT=SEP still alive (?) I just found the following in some IBM same JCL (job, actually): //SYSUT1 DD UNIT=(SYSDA,SEP=(SORTLIB,SYSLMOD,SYSLIN)), // SPACE=(1000,(60,20)) Last change date is half of the 2013 (creation date is probably 2005 or so). As far as I know SEP is syntax checked and ignored for many moons, at least since first OS/390, but I vaguely remember somebody told me it was obsoleted with advent of MVS. -- Radoslaw Skorupka Lodz, Poland -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: CPACF
Have a look at the CSFCCVT control block - described in SYS1.MODGEN. Hope that helps... Roger -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: CPACF
..forgot to addlook at File 771 on the CBT Tape (www.cbttape.org) and the ICSF Monitor. Roger -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: UNIT=SEP still alive (?)
On 29 August 2013 16:18, R.S. r.skoru...@bremultibank.com.pl wrote: I just found the following in some IBM same JCL (job, actually): //SYSUT1 DD UNIT=(SYSDA,SEP=(SORTLIB,SYSLMOD,SYSLIN)), // SPACE=(1000,(60,20)) Last change date is half of the 2013 (creation date is probably 2005 or so). As far as I know SEP is syntax checked and ignored for many moons, at least since first OS/390, but I vaguely remember somebody told me it was obsoleted with advent of MVS. I slightly more than vaguely remember it the same way. SEP= disappeared (was ignored) with MVS, i.e. OS/VS2 2.0, because it limited the then-new SRM's ability to swap a job in or out to control the I/O workload on a channel. There is an element of conflict between the application programmer/job owner's wish to have the best possible performance for an individual job by spreading its I/O around, vs the SRM's wish to control overall system performance as specified by the performance group definitions. Swapping out or in a job with allocations all over the place would not predictably change the load on an over or under busy channel. And on that note, I even more vaguely remember that SEP= (in pre-MVS OSs) was done at the channel level rather then the device, but that's so vague as to be unreliable. Since the source code for MVT and MVS 3.8 are both available online, anyone sufficiently interested can read the code and report back. On the matter of a recent piece of JCL containing these obsolete keywords, well that is all too common. There is a widespread and hard to break culture consisting of some blend of if it ain't broke, don't fix it, I'll just copy this JCL that works and change it minimally to suit my needs, and we're not really sure we need this anymore, but I don't want to be the one to remove it and find it breaks something important, so I'd better leave it in. I removed SEP= from one of our product manuals and around 2000, and when we acquired another product almost ten years later, I found its install manual to have SEP= too. I may yet have missed some... Tony H. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN