The library list on the AS/400 is similar to the "path" on PC's. Mainframe programmers may compare
it to the "steplib" or "joblib". It defines the order of libraries that the operating system
uses to find objects.
When you execute a command or call a program, the AS/400 must know where to find the command or program. Sometimes, you specify the library explicitly. But if you don't, the AS/400 will find your command or program by looking in each library in your library list. It will use the first one that it finds first.
This is very handy for testing. If you are testing a version of a program, you can put it in a test library which is at the top of your library list. Then, whenever you specify a program or refer to a file, the system will use any object it can find in the test library. If it can't find it there, it will look further through your library list until it finds it.
So, setting up a test environment is as simple as:
Once you have inserted the test library name in your library list, you will want to make sure everything is in the proper order. Use the DSPLIBL command to see your library list. You will probably see three types of list entries:
The WRKOBJ command will help see which object is being used. This command is similar to the directory ("dir") command on PC's. Use it to list objects in your library list.
So, if you have three copies of program, "PAYCALC", in different libraries, use the command WRKOBJ PAYCALC to see which copy of "PAYCALC" will be used. The command will list all objects named "PAYCALC" in the sequence that the AS/400 finds them . If you ever say to yourself in frustration, "I know I changed the program but it looks like I'm still running the original program", it's a pretty good bet that you're executing a different copy of the program than you think. This is only a fraction of the power of the WRKOBJ command. It is the easiest way to navigate through an undocumented system. When you are copying files to your test library, use special care with the logical files. It is easy to create a logical file that resides in a test library but updates a physical file in a different library.
Review of Commands Discussed:
When you execute a command or call a program, the AS/400 must know where to find the command or program. Sometimes, you specify the library explicitly. But if you don't, the AS/400 will find your command or program by looking in each library in your library list. It will use the first one that it finds first.
This is very handy for testing. If you are testing a version of a program, you can put it in a test library which is at the top of your library list. Then, whenever you specify a program or refer to a file, the system will use any object it can find in the test library. If it can't find it there, it will look further through your library list until it finds it.
So, setting up a test environment is as simple as:
- 1) Create a test library.
- 2) Put objects that you want to test in the library. These can be files, menus,
programs or any AS/400 object.
- 3) Insert the test library name into your library list, before your production libraries.
Once you have inserted the test library name in your library list, you will want to make sure everything is in the proper order. Use the DSPLIBL command to see your library list. You will probably see three types of list entries:
- 1) The SYS libraries have operating system objects. This is where the AS/400 commands and menus are contained.
- 2) The CUR library is your current library. This is your first user library and is where objects are created if you don't specify which library to use.
- 3) The USR libraries list your other user libraries.
The WRKOBJ command will help see which object is being used. This command is similar to the directory ("dir") command on PC's. Use it to list objects in your library list.
So, if you have three copies of program, "PAYCALC", in different libraries, use the command WRKOBJ PAYCALC to see which copy of "PAYCALC" will be used. The command will list all objects named "PAYCALC" in the sequence that the AS/400 finds them . If you ever say to yourself in frustration, "I know I changed the program but it looks like I'm still running the original program", it's a pretty good bet that you're executing a different copy of the program than you think. This is only a fraction of the power of the WRKOBJ command. It is the easiest way to navigate through an undocumented system. When you are copying files to your test library, use special care with the logical files. It is easy to create a logical file that resides in a test library but updates a physical file in a different library.
Review of Commands Discussed:
DSPLIBL - Display complete library list EDTLIBL - Edit library list CHGCURLIB - Change Current Library WRKOBJ - Work with objects (similar to PC "dir")Example of Library List Set Up for Testing:
QSYS SYS System Library QSYS2 SYS System Library for CPI's QHLPSYS SYS QUSRSYS SYS TESTFILES CUR Library for Test Files TESTPGMS USR Library for Test Programs GLFILES USR Library for Production G/L Files GLPGMS USR Library for Production G/L Programs PRPGMS USR Library for Production P/R Programs PRFILES USR Library for Production P/R Files TAATOOL USR Library for User Tools QGPL USR General Purpose Library QTEMP USR
source: http://www.texas400.com/tutas400toc.html
Tidak ada komentar:
Posting Komentar