IBM Mainframe Forum Index
 
Register
 
IBM Mainframe Forum Index Mainframe: Search Log in to check your private messages Log in
 

why SYSIN data cannot be concatenated?


 
IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
View previous topic :: :: View next topic  
Author Message
dejunzhu

Active User


Joined: 08 May 2008
Posts: 390
Location: China

PostPosted: Wed Oct 30, 2013 1:56 pm
Reply with quote

I have below step, wich is to issue DB2 REPAIR command to execute:
Code:
//STEP2 EXEC DSNUPROC,SYSTEM=DB21,UID='REPAIR',UTPROC=''
//DSNUPROC.SYSREC DD DUMMY                             
//DSNUPROC.SYSIN    DD  *                               
  REPAIR SET TABLESPACE                                 
//         DD  DSN=QUA.DS.PARM(QUA),DISP=SHR           
//         DD  DSN=&&TS,DISP=(OLD,PASS)                 
NOCOPYPEND                                             


but from log, I can see the command was not successfully constructed.
this is the log:
Code:
********************************* TOP OF DATA ******************
 DSNUGUTC - OUTPUT START FOR UTILITY, UTILID = CMD0200J         
 DSNUGTIS - PROCESSING SYSIN AS EBCDIC                         
 DSNUGUTC -  REPAIR                                             
2.14 DSNUCBRS -   SET TABLESPACE QUALIFIER. TESTTABLE             
 DSNUGBAC - UTILITY EXECUTION COMPLETE, HIGHEST RETURN CODE=0   
******************************** BOTTOM OF DATA ****************


that is , parameter NOCOPYPEND was not appended to the command.

I don't understand why this happened.

but from the log, I also found

Code:
NP   DDNAME   StepName ProcStep
     SYSIN    STEP2    DSNUPROC
     SYSIN                     


the second SYSIN contains 'NOCOPYPEND ' but not belongs to any step.
how can I resolve this?
Back to top
View user's profile Send private message
Bill Woodger

Moderator Emeritus


Joined: 09 Mar 2011
Posts: 7312
Location: Inside the Matrix

PostPosted: Wed Oct 30, 2013 2:08 pm
Reply with quote

It can be concatenated. You forgot to do so.

You needed // DD * before your last card. If you look at the processed JCL you'll see that the system generated a separate //SYSIN DD * for it, so that is where your card went.
Back to top
View user's profile Send private message
dejunzhu

Active User


Joined: 08 May 2008
Posts: 390
Location: China

PostPosted: Wed Oct 30, 2013 3:10 pm
Reply with quote

Thanks, Bill,
my bad...
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic All times are GMT + 6 Hours
Forum Index -> JCL & VSAM
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Forum Replies
No new posts How to find which file contains my se... DFSORT/ICETOOL 6
No new posts Changing Data Type SYNCSORT 4
No new posts Copying data from prev record using SORT SYNCSORT 19
No new posts how to get total count from numeric d... SYNCSORT 9
No new posts COBOL reading from SYSIN COBOL Programming 1

Back to Top