RE: CPYF Command Error?

From Darrel:

...As I know you understand, it boils down to knowing how CPYF actually 

works. The "why" is peripheral.

aec..>> For practical purposes, the important thing for programming is to know 
*how* something works, it's true. 

By the way, if in that program you really and truly always want the action to 
direct file activity to library LIBAAA, no matter what, where LIBAAA is 
whatever your library is, then all you have to do is to insert an OVRDBF 
immediately before the CPYF (or whatever else), with the SECURE() parameter 
specified:

OVRDBF FILEA TOFILE(LIBAAA/FILEA)  SECURE(*YES)
CPYF.....

And that override will protect your hard-coded library and overrule all other 
overrides...

So maybe they figured if you really really and truly want/need the hard-coded 
library name :-) you can always do that!

The command processing program wouldn't be able to distinguish between (1)the 
default *LIBL, (2)from a hard-coded *LIBL, (3)from a variable for the library 
name in the caller program that happened to contain the value *LIBL. 

So they probably had to decide in all these command processing programs just 
simply whether they were going to accept override redirects, or ignore them 
all. 

--Alan