Lizette, SOVDSSU is the same as DFDSS however when running under subsystem ExHPDM we need to use PGM=SOVDSSU. I found the error as per Willie's suggestion. Thanks to all who responded.
________________________________ From: Lizette Koehler <[email protected]> To: [email protected] Sent: Monday, 16 January 2012 8:11 AM Subject: Re: DFDSS QUESTION :ADR025E (002)-DEVSU(01), INPUT DEVICE TYPE IS INVALID FOR TASK > G'Day, > > I am trying to find the cause of my error while trying to execute a backup job using > DFDSS & ExHPDM. > > I get the error ADR025E (002)-DEVSU(01), INPUT DEVICE TYPE IS INVALID FOR TASK > which I cannot find why. > > Here is what my jcl looks like : > //STEP1 EXEC PGM=SOVDSSU,REGION=0M,TIME=1440 //SYSPRINT DD SYSOUT=* > //SYSUDUMP DD SYSOUT=* > //DSYSIN1 DD UNIT=SYSALLDA,VOL=SER=SYSIN1,DISP=SHR > //DSYSPP1 DD UNIT=SYSALLDA,VOL=SER=SYSPP1,DISP=SHR > //DSYSPP2 DD UNIT=SYSALLDA,VOL=SER=SYSPP2,DISP=SHR > //DSYS999 DD UNIT=SYSALLDA,VOL=SER=SYS999,DISP=SHR > > more dasd statments..... > > //TAPE01 DD DSN=SYSSHR.SOVDSSU.SYS.SYSIN1.C1(+1), > // DISP=(,CATLG,DELETE),SUBSYS=SOV > //TAPE11 DD DSN=SYSSHR.SOVDSSU.SYS.SYSIN1.C2(+1), > // DISP=(,CATLG,DELETE),SUBSYS=SOV > //TAPE02 DD DSN=SYSSHR.SOVDSSU.SYS.SYSPP1.C1(+1), > // DISP=(,CATLG,DELETE),SUBSYS=SOV > //TAPE22 DD DSN=SYSSHR.SOVDSSU.SYS.SYSPP1.C2(+1), > // DISP=(,CATLG,DELETE),SUBSYS=SOV > //TAPE03 DD DSN=SYSSHR.SOVDSSU.SYS.SYSPP2.C1(+1), > // DISP=(,CATLG,DELETE),SUBSYS=SOV > //TAPE33 DD DSN=SYSSHR.SOVDSSU.SYS.SYSPP2.C2(+1), > // DISP=(,CATLG,DELETE),SUBSYS=SOV > //TAPE04 DD DSN=SYSSHR.SOVDSSU.SYS.SYS999.C1(+1), > // DISP=(,CATLG,DELETE),SUBSYS=SOV > //TAPE44 DD DSN=SYSSHR.SOVDSSU.SYS.SYS999.C2(+1), > // DISP=(,CATLG,DELETE),SUBSYS=SOV > > more tape statements.... > > PARALLEL > DUMP FULL INDD(TAPE01) OUTDD(TAPE11) OPT(4) ALLDATA(*) ALLEXCP > DUMP FULL INDD(TAPE02) OUTDD(TAPE22) OPT(4) ALLDATA(*) ALLEXCP > DUMP FULL INDD(TAPE03) OUTDD(TAPE33) OPT(4) ALLDATA(*) ALLEXCP > DUMP FULL INDD(TAPE04) OUTDD(TAPE44) OPT(4) ALLDATA(*) ALLEXCP > > more dump statements. > > Error message: > > ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'PARALLEL ' > DUMP FULL INDD(TAPE01) OUTDD(TAPE11) OPT(4) ALLDATA(*) ALLEXCP ADR101I > (R/I)-RI01 (01), TASKID 002 HAS BEEN ASSIGNED TO COMMAND 'DUMP ' > DUMP FULL INDD(TAPE02) OUTDD(TAPE22) OPT(4) ALLDATA(*) ALLEXCP ADR101I > (R/I)-RI01 (01), TASKID 003 HAS BEEN ASSIGNED TO COMMAND 'DUMP ' > DUMP FULL INDD(TAPE03) OUTDD(TAPE33) OPT(4) ALLDATA(*) ALLEXCP ADR101I > (R/I)-RI01 (01), TASKID 004 HAS BEEN ASSIGNED TO COMMAND 'DUMP ' > DUMP FULL INDD(TAPE04) OUTDD(TAPE44) OPT(4) ALLDATA(*) ALLEXCP ADR101I > (R/I)-RI01 (01), TASKID 014 HAS BEEN ASSIGNED TO COMMAND 'DUMP ' ADR109I > (R/I)-RI01 (01), 2012.016 07:29:25 INITIAL SCAN OF USER CONTROL STATEMEN > ADR014I (SCH)-DSSU (02), 2012.016 07:29:25 ALL PREVIOUSLY SCHEDULED TASKS > COMPLE ADR025E (002)-DEVSU(01), INPUT DEVICE TYPE IS INVALID FOR TASK > ADR017E (002)-CLTSK(01), 2012.016 07:29:25 TASK NOT SCHEDULED DUE TO ERROR. > TASK ADR025E (003)-DEVSU(01), INPUT DEVICE TYPE IS INVALID FOR TASK ADR017E > (003)-CLTSK(01), 2012.016 07:29:25 TASK NOT SCHEDULED DUE TO ERROR. TASK > > I checked the esoteric, SYSALLDA is permitted. I cannot figure this one out. Any > suggestions? > I am not familiar with the program SOVDSSU. Is it similar to or does it call DFDSS? When was the last time it ran successfully coded this way? Perhaps you can remove one control card at a time and see which one complains? Maybe it uses the same parms as DFDSS and you could code PARM='TYPRUN=NORUN'? I would work from the bottom up. Lizette ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
