On 2019-05-08 2:39 PM, Peter wrote:
Does it really makes any difference between the two ?
That depends on what maintenance you have applied but not accepted.
I would guess that JCL using AMODGEN in the assembler SYSLIB
concatenation dates from (or is cloned from JCL that dates from) the
time when MVS did not have a SYS1.MODGEN data set.
In those days, to be sure to be sure that you were getting the latest
level of those macros for your system's maintenance level, placing
SMPMTS ahead of AMODGEN (and AHASPSRC etc. - that is, any macro DLIB
which did not have a corresponding SYSLIB) was the convention that was
supposed to be observed, even if it seldom was.
The creation of the relevant macro SYSLIBs such as MODGEN now places
them on an equal footing with libraries such as MACLIB in that regard.
For practical purposes these days, for assembler SYSLIB DD data sets
just change all AMODGEN references to MODGEN.
Anyone referenced AGENLIB lately?
:)
Cheers,
Greg
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
