Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

ISRSUPC -renaming OUTDD output dd statements or workaround?

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
PokerGuru

New User


Joined: 23 Jul 2010
Posts: 33
Location: Europe

PostPosted: Tue Jul 01, 2014 10:07 pm    Post subject: ISRSUPC -renaming OUTDD output dd statements or workaround?
Reply with quote

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
View user's profile Send private message

Rohit Umarjikar

Senior Member


Joined: 21 Sep 2010
Posts: 1609
Location: NY,USA

PostPosted: Wed Jul 02, 2014 12:42 am    Post subject:
Reply with quote

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
View user's profile Send private message
PokerGuru

New User


Joined: 23 Jul 2010
Posts: 33
Location: Europe

PostPosted: Wed Jul 02, 2014 4:34 pm    Post subject:
Reply with quote

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
View user's profile Send private message
Marso

REXX Moderator


Joined: 13 Mar 2006
Posts: 1218
Location: Israel

PostPosted: Wed Jul 02, 2014 5:17 pm    Post subject: Reply to: ISRSUPC -renaming OUTDD output dd statements or wo
Reply with quote

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=*
...

icon_question.gif
Back to top
View user's profile Send private message
PokerGuru

New User


Joined: 23 Jul 2010
Posts: 33
Location: Europe

PostPosted: Wed Jul 02, 2014 6:19 pm    Post subject:
Reply with quote

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
View user's profile Send private message
PokerGuru

New User


Joined: 23 Jul 2010
Posts: 33
Location: Europe

PostPosted: Wed Jul 02, 2014 6:45 pm    Post subject:
Reply with quote

Anyone else any suggestions or workarounds?
Back to top
View user's profile Send private message
daveporcelan

Active Member


Joined: 01 Dec 2006
Posts: 645
Location: Pennsylvania

PostPosted: Wed Jul 02, 2014 6:51 pm    Post subject:
Reply with quote

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
View user's profile Send private message
PokerGuru

New User


Joined: 23 Jul 2010
Posts: 33
Location: Europe

PostPosted: Wed Jul 02, 2014 6:59 pm    Post subject:
Reply with quote

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
View user's profile Send private message
daveporcelan

Active Member


Joined: 01 Dec 2006
Posts: 645
Location: Pennsylvania

PostPosted: Wed Jul 02, 2014 7:05 pm    Post subject:
Reply with quote

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
View user's profile Send private message
Marso

REXX Moderator


Joined: 13 Mar 2006
Posts: 1218
Location: Israel

PostPosted: Wed Jul 02, 2014 7:29 pm    Post subject: Reply to: ISRSUPC -renaming OUTDD output dd statements or wo
Reply with quote

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
View user's profile Send private message
PokerGuru

New User


Joined: 23 Jul 2010
Posts: 33
Location: Europe

PostPosted: Wed Jul 02, 2014 10:17 pm    Post subject:
Reply with quote

Thanks all.

Thanks Marso.
That will do it.
Back to top
View user's profile Send private message
Marso

REXX Moderator


Joined: 13 Mar 2006
Posts: 1218
Location: Israel

PostPosted: Thu Jul 03, 2014 4:57 pm    Post subject: Reply to: ISRSUPC -renaming OUTDD output dd statements or wo
Reply with quote

Glad to be of help.
It's hot enough, no need to light any fire under anybody's behind !
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Problem in writing Output file vickey_dw COBOL Programming 5 Mon Nov 14, 2016 11:14 pm
No new posts Syncsort - Hard coded Value in output PORYES SYNCSORT 1 Thu Nov 03, 2016 9:23 am
No new posts output data in CSV Format janmejay COBOL Programming 8 Sat Oct 15, 2016 2:20 pm
This topic is locked: you cannot edit posts or make replies. output data in CSV Format janmejay DFSORT/ICETOOL 3 Sat Oct 15, 2016 2:16 pm
No new posts ICETOOL/SYNCSORT - SYSPRINT output nartcr DFSORT/ICETOOL 17 Wed Oct 05, 2016 10:46 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us