Installation
of PTF03003
Automatic
copy of objects in the ACP(Acceptance) library to the user acceptance test
libraries (UAT) now extended to allow remote UAT areas. This means that the UAT
can be on a different machine.
After restoring the downloaded ptf software into the
FENIX library, use the DSPPGM (Display Program) or DSPOBJAUT (Display Object
Authority) command to identify the owner of the following programs in the
system library (FENIXQQQ), where QQQ is the FENIX environment
acronym. Delete the following programs:
Rename the following files in the same libarary
(FENIXQQQ):
1.
SCL076 to SCL076XX;
2.
SCL076L0 to
SCL076L0XX;
3.
SCL076L1 to
SCL076L1XX;
Re-activate the system (option 1, F17 & F18).
The new versions of the programs and files will
appear in library FENIXQQQ.
Change the ownership of the programs to what they
previously were. Copy the renamed files (XX) over the new files also in
FENIXQQQ using the FORMAT(*MAP *DROP) copy options. A new program, SCL174CL,
also in the same library should have the owner changed accordingly.
This PTF includes an enhancement to option 2
(Application Definition Maintenance) which provides for the maintenance of
the UAT environment definition.
Once an application has been selected for
maintenance via option 2, enter F14 to display the following screen:
SCL140 **** Test ABC System Environment **** 12/03/02 FENIX User Acceptance Test Environment 17:53:05 JAXWARD *Enquiry Apl:
HUMANR Desc: Human Resources
Application for ABC
UAT
number: 1 Descr: UAT Now allows for LCase too
Remote Destination no 1 RMTUATS1 UAT
Bib. Base de datos : UATHUM1 UAT Object
Library : UATHUM1 Data
*USE Authority : QUSER Object *USE
Authority : QPGMR Data
Owner : JSMITH Object Owner
: LISA Data
Authorisation List: HUDTAAUTL Object
Authorisation List: HUOBJAUTL Data
Auth. Ref. Object : Object Auth. Ref. Object : Data
Auth. Ref. Obj.Type:
Object Auth. Ref. Obj.Type: Data
Auth. Ref. Library :
Object Auth. Ref. Library : Copy
data sources to UAT : Y Lib: UATDTASR1
Replace
UAT data objects : Y Replace UAT objects
: Y Delete
UAT backout data objects : Y Delete UAT backout objects
: Y Delete
UAT Accepted data objs(A-P): N Delete UAT Accepted
objects : N ______________________________________________________________________________ F3=Exit F9=Add F5=Change
F11=Delete
F12=Cancel |
Definition
of UAT environments
The new fields permit the following:
Remote Destination no
This PTF allows the user to define the remote system
where the remote UAT libraries reside. The destination number (1-9998) defines
the location of the remote system as indicated via option 23 (Network File
Maintenance) with tranmission mode T (TCP/IP) and the User Id and Password
entered for access to the remote system via TCP/IP. Therefore, the
destination number must previously be defined in the network file. If defined,
the system will display the corresponding destination name.
Leave this field blank if the UAT area is on the
local machine.
NOTE: The other validation rules remain the same,
therefore, incase of remote UAT locations,although the libraries and other
fields (user profiles, Authorisation Lists) pertain to the remote location,
they must also exist on the local machine for validation purposes. No
validation is made for existence of these objects on the remote machine. They
simply must exist when the system is in place.
If this function is
to be used, FENIX must also be installed on the remote machine.