RE: Literal Libraries and Testing Problems

Perhaps you could use *CURLIB. Your programmer profiles set curlib to
the developer's test library, whereas all production users have
curlib=applib...

-Eric DeLong

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Wiant
Sent: Sunday, May 16, 2010 8:10 PM
To: Midrange Systems Technical Discussion
Subject: Literal Libraries and Testing Problems

It's not unusual (unfortunately) that much of our legacy code will use
CPYF like this: (usually to save copies of data before program
execution).

CPYF FROMFILE(file) TOFILE(library/file)

This obviously makes controlled testing difficult. I would like the
target library to be elsewhere.
My constraints are that :
1) I cannot change the code
2) I must run the complete job stream - I can't choose the bits and
pieces I want and customize the rest.

I'm trying to find a way to control this somehow. OVRDBF doesn't help
because the file names are the same. I thought of a DDMF in the target
library & pointing elsewhere, but of course that's a duplicate file name
in that library so I'm stuck again. There is no OVRLIB (override
library) command that I'm away of.

Does anyone have an idea how I could execute some function prior to
calling the offending program that would let me 'override' the target
library?

Thanks for any input

James P. Wiant



Quality is remembered long after the price is forgotten.
Slogan, Gucci Family


This message has been sent from Foodstuffs (Auckland) Limited
("Foodstuffs").

The information contained in this message and or attachments
is intended only for the person or entity to which it is
addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other
use of, or taking of any action in reliance upon, this
information by persons or entities other than the intended
recipient is prohibited. If you received this in error,
please contact the sender and delete the material from any
system and destroy any copies.

The views and opinions expressed in this message may be those
of the individual and not necessarily those of Foodstuffs,
and are not given or endorsed by it.

Please note that this communication does not designate an
information system for the purposes of the Electronic
Transactions Act 2002.