IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Regarding Dummy Parameter


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

Active User


Joined: 11 Apr 2008
Posts: 144
Location: Jamshedpur

PostPosted: Mon Sep 12, 2011 11:09 pm
Reply with quote

Hi All,

While analyzing the production JCL, i came across following dataset concatenation code -

Code:

//SNDUPDFL DD  DSN=XXXX.YYYYY.SNDUPD03,DISP=OLD   
//         DD  DSN=XXXX.YYYYY.SNDUPD04,DISP=OLD   
//         DD  DSN=XXXX.YYYYY.SNDUPD05,DISP=OLD   
//*        DD  DSN=XXXX.YYYYY.SNDUPD06,DISP=OLD   
//*        DD  DSN=XXXX.YYYYY.SNDUPD07,DISP=OLD   
//         DD  DSN=XXXX.YYYYY.SNDUPD08,DISP=OLD   
//*        DD  DSN=XXXX.YYYYY.SNDUPD10,DISP=OLD   
//         DD  DUMMY                             
//*        DD  DSN=XXXX.YYYYY.SNDUPD14,DISP=OLD   
//*        DD  DSN=XXXX.YYYYY.SNDUPD16,DISP=OLD   
//         DD  DSN=XXXX.YYYYY.SNDUPD18,DISP=OLD   
//         DD  DSN=XXXX.YYYYY.SNDUPD19,DISP=OLD   
//         DD  DSN=XXXX.YYYYY.SNDUPD21,DISP=OLD   
//*       DD  DSN=XXXX.YYYYY.SNDUPD24,DISP=OLD   
//*       DD  DSN=XXXX.YYYYY.SNDUPD26,DISP=OLD   
//*       DD  DSN=XXXX.YYYYY.SNDUPD33,DISP=OLD 
//         DD  DUMMY                             
//*       DD  DSN=XXXX.YYYYY.SNDUPD34,DISP=OLD           
//*       DD  DSN=XXXX.YYYYY.SNDUPD35,DISP=OLD         
//         DD  DUMMY                                     
//         DD  DSN=XXXX.YYYYY.SNDUPD36,DISP=OLD           
//*       DD  DSN=XXXX.YYYYY.SNDUPD37,DISP=OLD         
//         DD  DUMMY                                     
//*       DD  DSN=XXXX.YYYYY.SNDUPD11,DISP=OLD         
//*
                                             


When processing these files, the COBOL Code is processing only the first 4 files(files above dummy statement).

In the IBM manual it states that -

Quote:
The system treats data sets concatenated to a DUMMY data set as dummy data sets in that I/O operations are bypassed. However, the system performs disposition processing and allocates devices and storage for any concatenated data sets.


It says I/O opeartions are bypassed. Now the question, when they say I/O operations are bypassed do they mean nothing will be read after dummy statement. I am having difficulty in understanding that part of statement. As per the program behaviour I/O operations have been performed till first dummy statement is found and after that nothing was read. So the I/O operations will be bypassed from DD Dummy statement onwards. Please correct me, if i am wrong.
Back to top
View user's profile Send private message
Nic Clouston

Global Moderator


Joined: 10 May 2007
Posts: 2455
Location: Hampshire, UK

PostPosted: Tue Sep 13, 2011 12:07 am
Reply with quote

Quote:
The system treats data sets concatenated to a DUMMY data set as dummy data sets in that I/O operations are bypassed


You obviously do not understand the text in bold in that you do not seem to realise that the text 'I/O....bypassed' relates to the dummy datasets and its concatenated datasets. Also, the fact that the program managed to only read the files before the first DUMMY should have answered your question.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA

PostPosted: Tue Sep 13, 2011 12:15 am
Reply with quote

From section 4.5.1 of the JCL User's Guide manual:
Quote:
Requests to Read or Write a Dummy Data Set

When the program asks to read a dummy data set, an end-of-data-set exit is taken immediately. When the program writes to the dummy data set, the request is recognized but no data is transmitted. VSAM supports dummy data sets for both read and write processing. BSAM and QSAM support requests to write to a dummy data set. If any other access method is used, the job is terminated.
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Tue Sep 13, 2011 12:17 am
Reply with quote

Hello,

The JCL posted is at best confusing to look at.

Suggest it be cleaned up or documented as to why all of the nonsense is left in the convatenation . . .
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Mon Sep 19, 2011 8:32 pm
Reply with quote

saurabh39 wrote:
It says I/O opeartions are bypassed. Now the question, when they say I/O operations are bypassed do they mean nothing will be read after dummy statement. I am having difficulty in understanding that part of statement. As per the program behaviour I/O operations have been performed till first dummy statement is found and after that nothing was read. So the I/O operations will be bypassed from DD Dummy statement onwards. Please correct me, if i am wrong.
They are bypassed once they get to DUMMY, before that it is not.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> JCL & VSAM

 


Similar Topics
Topic Forum Replies
No new posts Using the Jobname parameter in a Qual... ABENDS & Debugging 1
No new posts Demand with DEADLINE TIME parameter CA Products 4
No new posts Option DYNALLOC second parameter. DFSORT/ICETOOL 11
No new posts Writing the output file name from a p... JCL & VSAM 7
No new posts Reference for COND parameter. JCL & VSAM 1
Search our Forums:

Back to Top