Joined: 09 Mar 2011 Posts: 7309 Location: Inside the Matrix
If the DCB is how you want:
In test, just ignore the message.
In other environments up to and including production, put your IDCAMS cards in a member of a PDS where you can get some control on them and at the same time keep them away from nosy JCL-checkers.
In other environments up to and including production, put your IDCAMS cards in a member of a PDS where you can get some control on them and at the same time keep them away from nosy JCL-checkers.
the nosy jcl checker complained not because of the REPRO,
but because it is just plain stupid...
since the dd statement has a dataclass any issues might come only at execution time
( just saw it, rereading the thread )
if the DATACLASS is defined properly ( contains the BLKLIMIT )
everything should work !
SMS will fill TAPE relevant DCB fields
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
I often wonder, how do such JCL-checkers get their place in the market? Is it because of the ignorance of members-of-the-team who actually decide what tool should be available at some shop or is it so trivial to think about it or...?
to waste resources by having people
sitting lazily in front of the screen
wandering thru the program in step mode
waiting for enlightenment
in more than 95% of the case just rereading the program would be enough
( for an half decent developer )
the program debugging time is shorter and leads to more understandable sources
using a debugger to fix bad programming habits is like ...
coud not fix the brakes and made the horn louder
1IDCAMS SYSTEM SERVICES TIME: 00:35:3
0
REPRO INFILE(DD1) OUTFILE(DD2)
0IDC3300I ERROR OPENING ENRICO.TEST.FB80.TAPE
IDC3321I ** OPEN/CLOSE/EOV ABEND EXIT TAKEN
0IDC0005I NUMBER OF RECORDS PROCESSED WAS 0
0IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12
0
0IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 12
as expected also no errors and IDCAMS return code 0
and anyway if the environment has been properly setup ...
here is a quote from the manuals about sdb and friends
Quote:
The block size limit is the first nonzero value from the following items:
BLKSZLIM value in the DD statement or dynamic allocation.
Block size limit in the data class. The SMS data class ACS routine can assign a data class to the data set. You can request a data class name with the DATACLAS keyword in the DD statement or the dynamic-allocation equivalent. The data set does not have to be SMS managed.
TAPEBLKSZLIM value in the DEVSUPxx member of SYS1.PARMLIB. A system programmer sets this value, which is in the data facilities area (DFA) (see z/OS DFSMSdfp Advanced Services).
The minimum block-size limit, 32 760.
