Re: When will ADRDSSU start to ENQUEUE on data sets?
Johnny, You may want to look into using Concurrent Copy with your backups. That way you won't lose datasets that are deleted after the start of the backup, and the actual backup will be closer to a real point-in-time image of all the datasets processed by the job. Ron -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Johnny Luo Sent: Tuesday, April 29, 2008 8:09 PM To: IBM-MAIN@BAMA.UA.EDU Subject: [IBM-MAIN] When will ADRDSSU start to ENQUEUE on data sets? Hi, We encountered a problem on our production system. A job was using DSS to backup a lot of data sets (logical dump) and we got ADR321E for one extended format PS data set: the data set was not on the supposed volume. This job will run more than 3 hours and we found out that another job will delete the data set and re-create it during that time (1.5 hours after the dump job starts). It might be the cause of ADR321E. And from the archive I found a similar thread: It is entirely possible that when DFDSS was building his process list the dataset was on the volume. Between that time the dataset probably got deleted and re-allocated. Naturally when DFDSS went to copy the dataset later on, it wasn't there. Hence the error message. Moral of the story: Don't delete datasets until after DFDSS has copied them. Does that mean there is a time interval between DSS located the data set via catalog and DSS actually places the ENQUEUE on it? If it's true, from our experience this time interval for a big dump job is very long. Thus give another job the chance to delete the target data set. Do we have any method to ask DSS to ENQUEUE earlier? Thanks. -- Best Regards, Johnny Luo -- 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
Re: When will ADRDSSU start to ENQUEUE on data sets?
Hello Johhny, over in IBM-MAIN-ARCHIVES http://bama.ua.edu/cgi-bin/wa?A2=ind0211L=ibm-main-archivesP=R107226 http://bama.ua.edu/cgi-bin/wa?A2=ind0202L=ibm-main-archivesP=R120423 There is a reference to Marketing Request MR00058723 On Wed, 30 Apr 2008 19:37:47 +0800, Johnny Luo [EMAIL PROTECTED] wrote: Bruce, 'Search the archives for earlier posts on DF/DSS using the older SVC26 interface to retrieve CATALOG data' I have tried various keywords but sill can not find the thread. Can you give more hints? Thanks. Regards Bruce Hewson -- 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
Re: When will ADRDSSU start to ENQUEUE on data sets?
Hello Johnny, Does your backup job use generic dataset masks for the INCLUDE list? Search the archives for earlier posts on DF/DSS using the older SVC26 interface to retrieve CATALOG data. In one case here a job took 2 hours to build the dataset list before mounting the first output tape. Changing the job by adding build-include-list step, before calling ADRDSSU, which uses REXX to call the IGGCSI00 Catalog Search Interface and built an explicit filter list (FILTERDD), reduced that wait time to 2 minutes. If you need to ENQUEUE on the dataset, just add //DD001 DD DISP=SHR,DSN=dataset1 etc to your backup JCL. On Wed, 30 Apr 2008 11:08:56 +0800, Johnny Luo [EMAIL PROTECTED] wrote: Hi, We encountered a problem on our production system. A job was using DSS to backup a lot of data sets (logical dump) and we got ADR321E for one extended format PS data set: the data set was not on the supposed volume. This job will run more than 3 hours and we found out that another job will delete the data set and re-create it during that time (1.5 hours after the dump job starts). It might be the cause of ADR321E. snip Best Regards, Johnny Luo Regards Bruce Hewson //MYUSERBLD JOB (ACCT#),'BUILD FILTER LIST', // CLASS=I, // MSGCLASS=X, // NOTIFY=SYSUID //* //* //BGTSOEXEC PGM=IKJEFT01,DYNAMNBR=100 //* //MASKLIST DD * SA%%.CICS.%%.DFHCSD SE%%.CICS.%%.DFHCSD SC%%.CICS.%%.DFHCSD /* //SYSTSIN DD * %BILDFILT MASKLIST /* //* //FILTERDD DD DISP=(NEW,PASS), // SPACE=(TRK,(1,1)), // DSORG=PS,LRECL=80,RECFM=FB,BLKSIZE=0, // DSN=amp;FILTERDD //* //* //SYSTSPRT DD SYSOUT=* //SYSPRINT DD SYSOUT=* //SYSPROC DD DISP=SHR,DSN=MYUSER.USER.CMDPROC //* //* //DUMPEXEC PGM=ADRDSSU,PARM='TYPRUN=NORUN' //FILTERDD DD DISP=(OLD,DELETE), // DSN=amp;FILTERDD //SYSPRINT DD UNIT=SYSDA,DISP=(NEW,CATLG),SPACE=(CYL,(2,1),RLSE), // DSN=MYUSER.DFDSS.TESTRUN.SYSPRINT,DCB=DSCB, // RECFM=VFB,LRECL=137,DSORG=PS //BACKUPDD DSN=MYUSER.DFDSS.TESTRUN.BACKUP, // UNIT=3390,SPACE=(CYL,(100,20),RLSE), // DISP=(,CATLG,DELETE) //SYSINDD * DUMP DATASET( - FILTERDD(FILTERDD) - ) - OUTDDNAME(BACKUP) - TOLERATE(ENQFAILURE) - SPHERE- CONCURRENT- SHARE /* //* // -- 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
Re: When will ADRDSSU start to ENQUEUE on data sets?
Bruce, Thanks a lot!!! I must say, it's a great idea. We have lots of job runing hours to backup data sets both in production and test environment and they all use generic filter. The possible performance gain is well worth doing and I will work on it right now. The rexx requires some work cause I don't want to change the way other people use DSS. So my rexx must be able to process any data set list syntax DSS recognizes. Thanks. On Wed, Apr 30, 2008 at 2:01 PM, Bruce Hewson [EMAIL PROTECTED] wrote: Hello Johnny, Does your backup job use generic dataset masks for the INCLUDE list? Search the archives for earlier posts on DF/DSS using the older SVC26 interface to retrieve CATALOG data. In one case here a job took 2 hours to build the dataset list before mounting the first output tape. Changing the job by adding build-include-list step, before calling ADRDSSU, which uses REXX to call the IGGCSI00 Catalog Search Interface and built an explicit filter list (FILTERDD), reduced that wait time to 2 minutes. If you need to ENQUEUE on the dataset, just add //DD001 DD DISP=SHR,DSN=dataset1 etc to your backup JCL. On Wed, 30 Apr 2008 11:08:56 +0800, Johnny Luo [EMAIL PROTECTED] wrote: Hi, We encountered a problem on our production system. A job was using DSS to backup a lot of data sets (logical dump) and we got ADR321E for one extended format PS data set: the data set was not on the supposed volume. This job will run more than 3 hours and we found out that another job will delete the data set and re-create it during that time (1.5 hours after the dump job starts). It might be the cause of ADR321E. snip Best Regards, Johnny Luo Regards Bruce Hewson //MYUSERBLD JOB (ACCT#),'BUILD FILTER LIST', // CLASS=I, // MSGCLASS=X, // NOTIFY=SYSUID //* //* //BGTSOEXEC PGM=IKJEFT01,DYNAMNBR=100 //* //MASKLIST DD * SA%%.CICS.%%.DFHCSD SE%%.CICS.%%.DFHCSD SC%%.CICS.%%.DFHCSD /* //SYSTSIN DD * %BILDFILT MASKLIST /* //* //FILTERDD DD DISP=(NEW,PASS), // SPACE=(TRK,(1,1)), // DSORG=PS,LRECL=80,RECFM=FB,BLKSIZE=0, // DSN=FILTERDD //* //* //SYSTSPRT DD SYSOUT=* //SYSPRINT DD SYSOUT=* //SYSPROC DD DISP=SHR,DSN=MYUSER.USER.CMDPROC //* //* //DUMPEXEC PGM=ADRDSSU,PARM='TYPRUN=NORUN' //FILTERDD DD DISP=(OLD,DELETE), // DSN=FILTERDD //SYSPRINT DD UNIT=SYSDA,DISP=(NEW,CATLG),SPACE=(CYL,(2,1),RLSE), // DSN=MYUSER.DFDSS.TESTRUN.SYSPRINT,DCB=DSCB, // RECFM=VFB,LRECL=137,DSORG=PS //BACKUPDD DSN=MYUSER.DFDSS.TESTRUN.BACKUP, // UNIT=3390,SPACE=(CYL,(100,20),RLSE), // DISP=(,CATLG,DELETE) //SYSINDD * DUMP DATASET( - FILTERDD(FILTERDD) - ) - OUTDDNAME(BACKUP) - TOLERATE(ENQFAILURE) - SPHERE- CONCURRENT- SHARE /* //* // -- 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 -- Best Regards, Johnny Luo -- 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
Re: When will ADRDSSU start to ENQUEUE on data sets?
I think there might be one issue you also need to deal with. This is old knowledge and I do not know if the limit still exists, but at one time DFDSS could only handle so many control cards at one time. The generic allowed you to handle 100's of files but specific data set backups had a limitation. I am thinking I remember that it could only handle 254 input files, but I could be wrong. Does anyone know if there is still a limitation on the number of input control cards for file names? For example, INC(DS(A.B, A.C, ... A.ZZZ.) Lizette -- Snip I must say, it's a great idea. We have lots of job runing hours to backup data sets both in production and test environment and they all use generic filter. The possible performance gain is well worth doing and I will work on it right now. The rexx requires some work cause I don't want to change the way other people use DSS. So my rexx must be able to process any data set list syntax DSS recognizes. -- UnSnip -- 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
Re: When will ADRDSSU start to ENQUEUE on data sets?
Yes, it exists. We're using z/OS 1.7 and the limitation forced me to use FILTERDD. The limitation is only for the SYSIN. On Wed, Apr 30, 2008 at 6:18 PM, Lizette Koehler [EMAIL PROTECTED] wrote: I think there might be one issue you also need to deal with. This is old knowledge and I do not know if the limit still exists, but at one time DFDSS could only handle so many control cards at one time. The generic allowed you to handle 100's of files but specific data set backups had a limitation. I am thinking I remember that it could only handle 254 input files, but I could be wrong. Does anyone know if there is still a limitation on the number of input control cards for file names? For example, INC(DS(A.B, A.C, ... A.ZZZ.) Lizette -- Snip I must say, it's a great idea. We have lots of job runing hours to backup data sets both in production and test environment and they all use generic filter. The possible performance gain is well worth doing and I will work on it right now. The rexx requires some work cause I don't want to change the way other people use DSS. So my rexx must be able to process any data set list syntax DSS recognizes. -- UnSnip -- 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 -- Best Regards, Johnny Luo -- 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
Re: When will ADRDSSU start to ENQUEUE on data sets?
Bruce, 'Search the archives for earlier posts on DF/DSS using the older SVC26 interface to retrieve CATALOG data' I have tried various keywords but sill can not find the thread. Can you give more hints? Thanks. On Wed, Apr 30, 2008 at 2:01 PM, Bruce Hewson [EMAIL PROTECTED] wrote: Hello Johnny, Does your backup job use generic dataset masks for the INCLUDE list? Search the archives for earlier posts on DF/DSS using the older SVC26 interface to retrieve CATALOG data. In one case here a job took 2 hours to build the dataset list before mounting the first output tape. Changing the job by adding build-include-list step, before calling ADRDSSU, which uses REXX to call the IGGCSI00 Catalog Search Interface and built an explicit filter list (FILTERDD), reduced that wait time to 2 minutes. If you need to ENQUEUE on the dataset, just add //DD001 DD DISP=SHR,DSN=dataset1 etc to your backup JCL. On Wed, 30 Apr 2008 11:08:56 +0800, Johnny Luo [EMAIL PROTECTED] wrote: Hi, We encountered a problem on our production system. A job was using DSS to backup a lot of data sets (logical dump) and we got ADR321E for one extended format PS data set: the data set was not on the supposed volume. This job will run more than 3 hours and we found out that another job will delete the data set and re-create it during that time (1.5 hours after the dump job starts). It might be the cause of ADR321E. snip Best Regards, Johnny Luo Regards Bruce Hewson //MYUSERBLD JOB (ACCT#),'BUILD FILTER LIST', // CLASS=I, // MSGCLASS=X, // NOTIFY=SYSUID //* //* //BGTSOEXEC PGM=IKJEFT01,DYNAMNBR=100 //* //MASKLIST DD * SA%%.CICS.%%.DFHCSD SE%%.CICS.%%.DFHCSD SC%%.CICS.%%.DFHCSD /* //SYSTSIN DD * %BILDFILT MASKLIST /* //* //FILTERDD DD DISP=(NEW,PASS), // SPACE=(TRK,(1,1)), // DSORG=PS,LRECL=80,RECFM=FB,BLKSIZE=0, // DSN=FILTERDD //* //* //SYSTSPRT DD SYSOUT=* //SYSPRINT DD SYSOUT=* //SYSPROC DD DISP=SHR,DSN=MYUSER.USER.CMDPROC //* //* //DUMPEXEC PGM=ADRDSSU,PARM='TYPRUN=NORUN' //FILTERDD DD DISP=(OLD,DELETE), // DSN=FILTERDD //SYSPRINT DD UNIT=SYSDA,DISP=(NEW,CATLG),SPACE=(CYL,(2,1),RLSE), // DSN=MYUSER.DFDSS.TESTRUN.SYSPRINT,DCB=DSCB, // RECFM=VFB,LRECL=137,DSORG=PS //BACKUPDD DSN=MYUSER.DFDSS.TESTRUN.BACKUP, // UNIT=3390,SPACE=(CYL,(100,20),RLSE), // DISP=(,CATLG,DELETE) //SYSINDD * DUMP DATASET( - FILTERDD(FILTERDD) - ) - OUTDDNAME(BACKUP) - TOLERATE(ENQFAILURE) - SPHERE- CONCURRENT- SHARE /* //* // -- 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 -- Best Regards, Johnny Luo -- 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
When will ADRDSSU start to ENQUEUE on data sets?
Hi, We encountered a problem on our production system. A job was using DSS to backup a lot of data sets (logical dump) and we got ADR321E for one extended format PS data set: the data set was not on the supposed volume. This job will run more than 3 hours and we found out that another job will delete the data set and re-create it during that time (1.5 hours after the dump job starts). It might be the cause of ADR321E. And from the archive I found a similar thread: It is entirely possible that when DFDSS was building his process list the dataset was on the volume. Between that time the dataset probably got deleted and re-allocated. Naturally when DFDSS went to copy the dataset later on, it wasn't there. Hence the error message. Moral of the story: Don't delete datasets until after DFDSS has copied them. Does that mean there is a time interval between DSS located the data set via catalog and DSS actually places the ENQUEUE on it? If it's true, from our experience this time interval for a big dump job is very long. Thus give another job the chance to delete the target data set. Do we have any method to ask DSS to ENQUEUE earlier? Thanks. -- Best Regards, Johnny Luo -- 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
Re: When will ADRDSSU start to ENQUEUE on data sets?
There is a delay between the building of the list and actually backing up each dataset on the list. Generally, an enqueue is not set at the time the list is built - as you said, it may be hours before each dataset is actually backed up. Do you run DSS natively or are you calling it from another product, perhaps CA-Disk? If you are using DSS under the covers of CA-Disk, you can pass a parm (on the SYSPARMS dd statement) to enqueue the dataset. That may cause problems for your batch processing - enqueues can cause jobs to have to wait, which can cause time-outs or other problems, depending on what the jobs are doing. You could also have CA-Disk retry, which in your case could result in the new version of the dataset being backed up. That might be okay or not, depending on what you need to do. I would think that a better approach would be to look at the back up needs for that dataset and make changes accordingly. You might move the backup instream of the job that deletes and rebuilds the dataset or maybe tell your scheduling system not to run one job until the other is finished, whatever would fit your situation best. You might want to look at the possibility of breaking up the back up job into multiple jobs, each backing up one storage group or the contents of one catalogue at a time (just as an example). Linda Mooney -- Original message -- From: Johnny Luo [EMAIL PROTECTED] Hi, We encountered a problem on our production system. A job was using DSS to backup a lot of data sets (logical dump) and we got ADR321E for one extended format PS data set: the data set was not on the supposed volume. This job will run more than 3 hours and we found out that another job will delete the data set and re-create it during that time (1.5 hours after the dump job starts). It might be the cause of ADR321E. And from the archive I found a similar thread: It is entirely possible that when DFDSS was building his process list the dataset was on the volume. Between that time the dataset probably got deleted and re-allocated. Naturally when DFDSS went to copy the dataset later on, it wasn't there. Hence the error message. Moral of the story: Don't delete datasets until after DFDSS has copied them. Does that mean there is a time interval between DSS located the data set via catalog and DSS actually places the ENQUEUE on it? If it's true, from our experience this time interval for a big dump job is very long. Thus give another job the chance to delete the target data set. Do we have any method to ask DSS to ENQUEUE earlier? Thanks. -- Best Regards, Johnny Luo -- 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
