Again, with above/below stuff.
It is a FACT that today, and ever since MVS/370 in 1973, the "native"
interface to JES2 and JES3 is VSAM ACBs / RPLs. When you are using a
DCB to write data to a JES2 or JES3 SPOOL, you are actually going through
a compatibility interface.
However, I would like to comment that using the ACB / RPL interface is not
a good idea. The reason it is not a good idea is you cannot use JCL to
direct output to a real data set, or to a SPOOL data set.
The only positive advantage to using the ACB / RPL interface is you
can ENDREQ to a INTRDR to terminate the job being submitted, and also
retrieve the JES2 job ID assigned to the job in RPLRBAR.
The physical DCB must be below the line. However, the OPEN, PUT, GET,
and CLOSE macros can all execute AMODE 31, and can execute above the line.
Quote:
>Has anyone heard (rumors or fact) that JES will (eventually?) support
>the use of VSAM ACB's and RPL's so that there will never again (hah!)
>be a need to be concerned with "The line" as far as I/O is concerned
>from a problem program POV? For instance, you can process all of
>the VSAM stuff you want, and all of it works very well in 31 bit mode,
>but if you have any kind of output directed at spool, you still have to
>use a DCB, and that means that "something" in your program still
>has to concern itself with this line thing...
>*** Posted from RemarQ - http://www.remarq.com - Discussions Start Here (tm) ***
-- Steve Myers
The E-mail addresses in this message are private property. Any use of them
to send unsolicited E-mail messages of a commerical nature will be
considered trespassing, and the originator of the message will be sued in
small claims court in Camden County, New Jersey, for the maximum penalty
allowed by law.