Test & Production File Write issues

15 pts.
test lab
Test systems
I'm creating a new test environment. I made a user called TEST01 with a new testing job description, I've added the test library to the top of TEST01's library list. The files and programs were complied using the test library. I ran the program and it created a new part as it was supposed to do in the test file. However it duplicated the new part in production. What am I missing? I've checked the compiles and they do not contain production libraries. I displayed the active libraries while the job was running and they were all the correct library. Thanks for your help.

Software/Hardware used:
OS/400 v5 r4

Answer Wiki

Thanks. We'll let you know when a new response is added.

I doubt that it created the part in both files.

How do you “see” the new part? Through your application?

I can think of two ways this could happen,
1. the application uses a logical file, in building the test you must compile the required physical files first, then the logical files. If a logical is compiled first the system will search the library list until it finds a physical and create the logical pointing at it. You can tell where your logicals are pointing by using the DSPFD command with the logical file name. You could also tell what logicals are attched to a physical with the DSPPFREF command.

2. Your application is targeted at files in production. It could be using OVRDBF commands in the CL or RPG programs, RPG F specs with extfile command, or logical or views, or SQL’s that specifically define the library to use.

While your application is on the view/create part screen use another session to run WRKUSRJOB – F14 will show the files in use including the libraries. There is also an option to see the Overrides.

Hope this helps

Discuss This Question: 1  Reply

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Lk58
    Phil, Thanks for your help. I rechecked the logicals and they were pointed to production files. I believe the job description or library list was incorrect when they were compiled. The thing that threw me yesterday was when the job was running I did a WRKACTJOB and displayed the open files and they were all, including the LF's coming from the test library. Thanks again, Larry
    15 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: