|
View previous topic :: View next topic
|
| Author |
Message |
PokerGuru
New User
Joined: 23 Jul 2010
Posts: 33
Location: Europe
|
|
|
|
Can anyone point me to manual, or does anyone know is there any way I can change the OUTDD statements for ISRSUPC to number them or another workaround?
I have tried OUTDD1 and OUTDD2 but this fails.
I need them named different things as the test automation framework I am using only checks the first Output DD if there are more than one named the same, so in this case my framework only checks for specific output in the first OUTDD output, but doesn't find anything in all other OUTDD compare outputs in the job.
I could split the job up obviously into numerous different jobs, but there are a lot of ISRSUPC compares in each job so this would be very laborious.
| Code: |
//SUPERC1 EXEC PGM=ISRSUPC,
// PARM=(DELTAL,LINECMP,
// '',
// '')
//OLDDD DD DSN=QARESM1.QAR126.OLD1.SPLIT.SPINDEX,
// DISP=SHR
//NEWDD DD DSN=QARESM1.QAR126.OLD1.SPLIT.SPINDEX2,
// DISP=SHR
//OUTDD DD SYSOUT=*
/*
//SUPERC2 EXEC PGM=ISRSUPC,
// PARM=(DELTAL,LINECMP,
// '',
// '')
//OLDDD DD DSN=QARESM1.QAR127.NEW1.SPLIT.SPINDEX,
// DISP=SHR
//NEWDD DD DSN=QARESM1.QAR127.NEW1.SPLIT.SPINDEX2,
// DISP=SHR
//OUTDD DD SYSOUT=*
|
[/code] |
|
| Back to top |
|
 |
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010
Posts: 3051
Location: NYC,USA
|
|
|
|
| I don't think you can change that, but you may add another step after OUTDD to copy into another file with a new DD name as you want everytime. |
|
| Back to top |
|
|
PokerGuru
New User
Joined: 23 Jul 2010
Posts: 33
Location: Europe
|
|
|
|
Thanks for the suggestion, but the problem with this is, the framework only looks for desired output from sysview output for the job, not from files.
Any other suggestions? |
|
| Back to top |
|
|
Marso
REXX Moderator
Joined: 13 Mar 2006
Posts: 1353
Location: Israel
|
|
|
|
What about using:
| Code: |
//SUPERC1 EXEC PGM=ISRSUPC,
...
//OUTDD DD DDNAME=OUTDD1
//OUTDD1 DD SYSOUT=*
...
//SUPERC2 EXEC PGM=ISRSUPC,
...
//OUTDD DD DDNAME=OUTDD2
//OUTDD2 DD SYSOUT=*
... |
 |
|
| Back to top |
|
|
PokerGuru
New User
Joined: 23 Jul 2010
Posts: 33
Location: Europe
|
|
|
|
Unfortunately Marso that doesn't work. It completes without problems,
but there is no OUTDD1 and OUTDD2 output displayed in sysview for the job. I only have the following sysview output:
JobName JobId Queue Datasets
REGRES01 JOB21665 OUTPUT 13
----------------------------------------
Cmd DDname Stepname Procstep Stat
________ JESMSGLG JES2 HELD
________ JESJCL JES2 HELD
________ JESYSMSG JES2 HELD
________ SYSPRINT PRECLEAN HELD
________ SYSPRINT STEPOLD1 HELD
________ SYSPRINT STEPOLD2 HELD
________ SYSPRINT $$$$$$@ HELD
________ SYSPRINT STEPNEW1 HELD
________ SYSPRINT STEPNEW2 HELD
________ SYSPRINT $$$$$$@ HELD
________ OUTDD SUPERC1 HELD
________ OUTDD SUPERC2 HELD
________ SYSPRINT CLEANUP HELD |
|
| Back to top |
|
|
PokerGuru
New User
Joined: 23 Jul 2010
Posts: 33
Location: Europe
|
|
|
|
| Anyone else any suggestions or workarounds? |
|
| Back to top |
|
|
daveporcelan
Active Member
Joined: 01 Dec 2006
Posts: 792
Location: Pennsylvania
|
|
|
|
From the first post:
| Quote: |
| I need them named different things as the test automation framework I am using only checks the first Output DD if there are more than one named the same, so in this case my framework only checks for specific output in the first OUTDD output, but doesn't find anything in all other OUTDD compare outputs in the job. |
My suggestion is modify the test automation to fit your need.
From the last post:
| Quote: |
| Anyone else any suggestions or workarounds? |
Do not solicit for any additional help. It will come if it will come. It will not if you ask to hard. |
|
| Back to top |
|
|
PokerGuru
New User
Joined: 23 Jul 2010
Posts: 33
Location: Europe
|
|
|
|
Okay thanks.
The automation team have told me the framework would get out of control if they have to check for multiple output strings, in different output DD's all with the same name - OUTDD. So this isn't an option. So what I am trying to achieve now is changing these outdd's to different names, then the automation team can update the framework to search for my multiple strings in each of these uniquely named output DD's. |
|
| Back to top |
|
|
daveporcelan
Active Member
Joined: 01 Dec 2006
Posts: 792
Location: Pennsylvania
|
|
|
|
I work in the Automation arena myself.
If I gave the excuse that it would get out of control, so I couldn't do it....
My boss would light a fire under my behind.
Maybe their boss needs to do the same.
Good luck. |
|
| Back to top |
|
|
Marso
REXX Moderator
Joined: 13 Mar 2006
Posts: 1353
Location: Israel
|
|
|
|
One more suggestion:
| Code: |
//SUPERC1 EXEC PGM=ISRSUPC,
...
//OUTDD DD DISP=(NEW,PASS),DSN=&OUTDD1,...
...
//SUPERC2 EXEC PGM=ISRSUPC,
...
//OUTDD DD DISP=(NEW,PASS),DSN=&OUTDD2,...
...
//LASTSTEP EXEC PGM=IEBGENER
//SYSUT1 DD DISP=(OLD,DELETE),DSN=&OUTDD1
// DD DISP=(OLD,DELETE),DSN=&OUTDD2
...
//SYSUT2 DD SYSOUT=*
//SYSPRINT DD SYSOUT=* |
If you don't mind having all your results concatenated into a single output,
all you need now is collecting SYSUT2 in the last step. |
|
| Back to top |
|
|
PokerGuru
New User
Joined: 23 Jul 2010
Posts: 33
Location: Europe
|
|
|
|
Thanks all.
Thanks Marso.
That will do it. |
|
| Back to top |
|
|
Marso
REXX Moderator
Joined: 13 Mar 2006
Posts: 1353
Location: Israel
|
|
|
|
Glad to be of help.
It's hot enough, no need to light any fire under anybody's behind ! |
|
| Back to top |
|
|
|
|
