RE: calling commands in unknown (at compile time)

Hi:

This requires another step. First *remove* the "target" library from the 
job library list, MONMSG, *then* add it, in first position, MONMSG.

This avoids the trap of the target library already existing in the job 
library list. If an add to first position is attempted for a library 
already in the list, CPF2103 is issued and the library remains in the 
original position. If  that position is lower in the list than another 
library that contains a copy of the command or program, that incorrect 
copy will be executed.

Darrell

Darrell A. Martin  -  754-2187
Manager, Computer Operations
dmartin@xxxxxxxxxxxxx

The other way to do it to simply add the library to the top of the
library list, with a MONMSG in case it is already there, before calling
the command. Then it finds the copy in that library first.

This e-mail, including attachments, may contain information that is 
confidential and/or proprietary, and may only be used by the person to 
whom this email is addressed. If the recipient of this e-mail is not the 
intended recipient or an authorized agent, the reader is hereby notified 
that any dissemination, distribution, or copying of this e-mail is 
prohibited. If this e-mail has been delivered to you in error, please 
notify the sender by replying to this message and deleting this e-mail 
immediately.