Documentation >
MAC-PAC Reference and Help >
Technical Support >
Key Concepts and Procedures >
Operation Procedures >
Creating a Duplicate MAC-PAC Data Environment
Creating a Duplicate MAC-PAC Data Environment
MAC-PAC allows you to use its object library with several data libraries. For certain situations, it can be useful to create a separate MAC-PAC data environment. For example, you can have one environment for production and a second for testing. Once created, this testing environment can be accessed through a different user profile than the production environment.
In MAC-PAC, creating a separate data environment simply means creating a separate data and recovery library. The object library can be used with both data libraries without conflict.
Library List
When you sign-on, your library list determines what MAC-PAC environment you will access. The list should contain MAC-PAC specific libraries as well as system libraries. See your system administrator for a list of the system libraries needed for your library list. Figure 1 shows the MAC-PAC specific library list for the production environment.
|
|
AADAT
|
The MAC-PAC production data library
|
AAPGM
|
The MAC-PAC object library
|
AARCV
|
The MAC-PAC production recovery library
|
AASRCxx
|
The MAC-PAC version xx source library
|
The Library List for the Production Environment.
These libraries are the MAC-PAC portion of the list.
Figure 2 shows the MAC-PAC specific library list for the new test environment you will be creating. You will need to create both the data (AADATTST) and recovery (AARCVTST) libraries.
|
|
AADATTST
|
The MAC-PAC test data library
|
AAPGM
|
The MAC-PAC object library
|
AARCVTST
|
The MAC-PAC test recovery library
|
AASRCxx
|
The MAC-PAC version xx source library
|
The library list for the New Test Environment.
These libraries are the MAC-PAC portion of the list.
Step-by-Step
To create a separate data environment follow these steps. Assume the production data library is called AADAT and the new data library is called AADATTST.
1. Have all users sign-off from the production environment. Sign-on as AAUSER.
2. Use the Recover Management module to change the journal receiver in your production library (AADAT). Backup this library if necessary. See the Recovery Management section in this manual.
3. End journaling in the production library (AADAT) using the command:
ENDJRNPF FILE(*ALL) JRN(AADAT/RMJRN)
4. Delete the journal in the production library (AADAT) with the command:
DLTJRN JRN(AADAT/RMJRN)
5. Delete the journal receiver in the production library (AADAT) with the command:
DLTJRNRCV JRNRCV(AADAT/RMRCVxxxx)
where xxxx is the number of the receiver
Note: Your journal receiver may be in a separate recovery library. If so, replace AADAT in the command with the name of your recovery library.
6. Save the production library (AADAT) using the command:
SAVOBJ OBJ(*ALL) LIB(AADAT) DEV(tape device name) ACCPTH(*YES)
7. Restore the saved library (AADAT) to the system into the new data library (AADATTST) using command:
RSTOBJ OBJ(*ALL) SAVLIB(AADAT) DEV(tape device name) RSTLIB(AADATTST)
8. Use the Recover Management module to start journaling in your production environment. From the Recovery Management Menu choose:
a. Option 11 to create a new journal receiver. Parameters are:
JRNRCV(RMRCV) LIB(AARCV)
b. Option 12 to create a new journal. Parameters are:
JRN(RMJRN) LIB(AADAT) JRNRCV(RMRCV) LIB(AARCV)
c. Option 10 to start journaling. There are no necessary parameters.
See the Recovery Management section in this manual for more details. You are now finished with the production environment. Users may begin using this environment again.
9. Create a new recovery library (AARCVTST) for your test environment using the command:
CRTLIB LIB(AARCVTST) TEXT(MAC-PAC Recovery Library - Test Environment)
If your AS/400 has a separate user auxiliary storage pool (ASP) there are benefits to creating the new recovery library there such as performance and recovery. If you wish to take advantage of these benefits you should create the new recovery library there. The command for this would be:
CRTLIB LIB(AARCVTST) TEXT(MAC-PAC Recovery Library - Test Environment) ASP(#)
# - the number of your user ASP.
See your system administrator and the appropriate IBM manual for details on user ASPs.
10. Create a new user profile for the test environment. This profile will utilize the test data library (AADATTST) and the test recovery library (AARCVTST). The new user profile should have the same attributes as the current production user profile except the initial program (MASIGNON) should reference the new data library (AADATTST) instead of the production data library.
11. Sign-on as the user profile you created in step 10. Use the command EDTLIBL to edit your library list. Add the new test data library (AADATTST) on top and the production program library (AAPGM) under this. Use the command "Call CFSPMENU", to enter the Sytem Processing Menu. Select System Support Menu (option 5).
12. Use the Reference File Maintenance conversation to update the Reference File category Z03 to use the new test data library (AADATTST) and new test recovery library (AARCVTST). Be sure to update both the data library and recovery library fields. The rest of the libraries on Reference File category Z03 should be left the same. See Figure 1 for a sample detail screen for Reference File category Z03. Update catagory E16 (MAC-PAC security officer password) to reflect the name of the new user created in step 10.
WILLIAMS COMMON FEATURES 1/11/93
DSP01 REFERENCE FILE CATEGORY Z03 INQUIRE
Category Name INSTALLATION LIBRARIES
BLANK KEY
Category Key
DATA LIBRARY OBJECT LIBRARY
Data AADATTST
XXXXXXXXXX XXXXXXXXXX
USER MODIFIED SOURCE LIBRARY AC MODIFIED SOURCE LIBRARY
Data
XXXXXXXXXX XXXXXXXXXX
STANDARD SOURCE LIBRARY RECOVERY LIBRARY
Data AARCVTST
XXXXXXXXXX XXXXXXXXXX
F2=Command F3=Exit F9=Inquiry F10=Function Select
|
Reference File category Z03 Detail Screen.
Used to change the date library for a new data environment.
13) Change all the job descriptions in the new data library (AADATTST) to reflect the new data and recovery libraries. Use the command:
CHGJOBD JOBD(AADATTST/jobd) INLLIBL(*)
* Be sure the initial library list is the same as the one on your current, production library list except the production data library (AADAT) should be replace with the new data library (AADATTST) and the production recovery library (AARCV) should be replaced with the new recovery library (AARCVTST). See Figure 2 for the test environment library list.
Figure 4 shows all the job descriptions used in MAC-PAC. All of them should be updated with the new library list.
|
|
APJOBD
|
Accounts Payable Job Description
|
ARJOBD
|
Accounts Receivable Job Description
|
BCASYNCJOB
|
Electronic Data Collection Asynchronous Job Description
|
DMJOBD
|
Draft Management Job Description
|
ECASYNCJOB
|
Expert Configurator Asynchronous Job Description
|
GAASYNCJOB
|
SYNCHRO Asynchronous Job Description
|
GLJOBD
|
General Ledger Job Description
|
JTASYNCJOB
|
Just-In-Time Asynchronous Job Description
|
MPASYNCJOB
|
MAC-PAC Asynchronous Job Description
|
MPPROCJOB
|
MAC-PAC Processing Job Description
|
POASYNCJOB
|
Purchasing Asynchronous Job Description
|
Job Descriptions in the New Test Data Library (AADATTST).
Each of these job descriptions needs to be updated with the new test environment library list.
14. Use the Recover Management module to start journaling in your new test environment. From the Recovery Management Menu choose:
a. Option 11 to create a new journal receiver. Parameters are:
JRNRCV(RMRCV) LIB(AARCVTST)
b. Option 12 to create a new journal. Parameters are:
JRN(RMJRN) LIB(AADATTST) JRNRCV(RMRCV) LIB(AARCVTST)
c. Option 10 to start journaling. There are no necessary parameters.
See the Recovery Management section in this manual for more details. You have now finished creating the new test environment. After performing needed menu authorizations, users may begin using this new environment.
Note: The menu files in the new environment will stay the same as they were in the old environment. You should enter the Menu Authorization conversation and make any menu/option changes you want in the new data environment before users begin working there.
You should perform all system maintenance functions on the new test library that you would on the production library. See the Operation Procedures portion of this manual for more information.