Jon Perryman added, re our RELINK job:
>You've been lucky so far. I've never used autocall nor library but
>SMP/e might not relink correctly depending upon your definitions.
>Typically object files are not retained in the SMP/e target. Instead,
>SMP/e typically does an include for the load module and issues a
>replace for object files to be replaced. For autocall, this logic
>might be something that Kurt can clarify.

Maybe I should kill the RELINK job then?

And re the USS files:
>If you can't figure out how to do this correctly, then look at an IBM
>example. For instance, you will see things like:

>//SYSLMOD DD PATH='/path/name/irrelevant'
>//*LIBRARYDD=UNIXLOAD

>where UNIXLOAD is a DDDEF specifying the actual filename. How is this
>that won't fly when every sysprog is accustomed to using UCLIN DDDEF
>to create their maint environment?

Not a sysprog (well, not a z/OS sysprog), so I'm not accustomed to anything 
like that. Is the *LIBRARYDD a comment or a majick SMP/E thing like 
//*CALLLIBS=YES ? If the latter, where is it documented? I don't see it in the 
packaging book or the SMP/E book.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to