IBM Mainframe Forum

I am creating an AFP file of labels to be iebgener'd from the mainframe to an attached laser INFOPRINT printer. I will need to create approximately 24 files per day. Because of the special label paper involved, I'd like to strip off the standard MVS/JES JOB start and end sheets (3 per print job).

//------- JOB (-----------),MSGCLASS=P,
// CLASS=X
//OUTCARD OUTPUT FORMDEF=A10110,PAGEDEF=LB3X4G,
//* CHARS=BX24,FORMS=1852,DEST=LOCAL
// CHARS=BX24,FORMS=1552,DEST=LOCAL
//STEP01 EXEC PGM=IEBGENER
//SYSUT1 DD DSN=-------.TEST.TRAYTAG.SIP1,DISP=SHR
//SYSUT2 DD SYSOUT=C,OUTPUT=*.OUTCARD
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY

I'm wondering whether this can be handled in the JCL or in the formdef.
We have 2 printers - one is for test. The Infoprint 1852 is production.

Thanks,
Katie

just use a different sysout class..
it has been a standard practice used for at least 40 years
simple, effective, and ... without any alternatives

follow on ...
hit the enter key too quickly, before rereading and the info given
was not completely correct

ask Your support , they should know how the system was setup
IIRC ( seen it a very long time ago ) there should be an option to turn off
separator pages for AFP printers

if the issue is critical to Your organization a jes exit might take care of it

or with proper operator coordination a jes command could be used to disable
the printing of separator pages

An operator can specify that separator pages are not to be produced by entering JES commands from the console.

Example: For JES2: $T PRT(nnnn),NOSEP

Example: For JES3: *CALL,WTR,OUT=nnnn,H=N,B=N

but is as You say the printer needs a special setup the coordination should be easy enough

Thanks! I will pass this on to the systems people. Someone suggested that it could be handled in the formdef. I did try playing around with sysout classes but got nowhere. However I think your add-on suggestions might put us in the right direction. I'll report back when I figure out just who and what can get this accomplished.

I will not need to use the JCL to handle the issue. We were planning on sending the output to CA-Deliver so that it will be easy to do re-prints. It is apparently easy for the administrators to code the package so that the sheets we don't need are not printed.

Thanks for the various suggestions. There are usually 100 ways to skin a cat.....