PCSACC/400_BUSCH&PARTNER, SOFTWARE

PCSACC/400 Second time installation V4R1M3

Step 1: Installation requirements

Required version of OS/400: This program require V4R3 of OS/400 or later. It is tested up to V6R1.
Please follow the attached Ptf informations.

You may upgrade from any version of PCSACC/400 (V2R1M05 - V4R1M2) directly to this release.

With this release you´ll need a new license code.

If you have a permanent license key per 2006/12/22, a new license key (with maintenace ending at 2007/03/31) will automatically be stored in library QPCS. With payment of the current maintenance invoice you´ll automatically get a new license key for another 12 months via email.

Step 2: Check of the disk allocation for the reduction of the installation time

It is urgently recommended to print a summary overview using command PRTSPC SUMMERY(*ONLY) in order to avoid an installation time of multiple hours. In case the logged protocol files exceed 1-200 MB, it might be useful to convert the logged data into authorities or delete them before starting the second time installation (using command CLRPFM QPCS/PCOUT and CLRPFM QPCS/PCOUT2).

Conversion can be submitted to batch with command CHGPCS - option 05 and in Programm DSPUSR option S and F17. Please take into consideration, that this batch job may run multiple hours when converting Gigabytes (= more than 100.000 records per user), depending on power, available DASD capacity and CPU usage of your iSeries (AS/400). The batch jobs can be cancelled at any time. Data will not be lost.

Reorganization of data (RGZPCS) prior to installation is not required.

Step 3: Remove working libraries from last installation

Please proofe if libraries QPCSO, QPCSO2924, QPCSO2929 and/or QPCSO2939 are stored on your system before installation,
using command WRKLIBPDM QPCSO*.

These libraries contain an old version of PCSACC/400 and have to be deleted before the new installation or the installation process was canceled.

Step 4: End workmanagement job's for active exit programs

Command PCSNETA and option F9 has to be used in order to end subsystems QSERVER and QUSRWRK (V5RX), to end TCP/IP FTP and eventually TCP/IP TELNET if a PCSACC/400 version V3R1M1 or higher is being replaced and TELNET exit programs have been activated. Use F2 in order to end all necessary workmanagement jobs and confirm execution by pressing F2.

If TCP/IP TELNET has to be stopped because corresponding exit programs are active, this may only be performed from the system console or another SNA terminal.

Another possibility is:

Remove all exit programs with option 4 from registration and end program PCSNETA without execution of specified workmanagement actions.

Followed by a nightly IPL - no more exit programs should be active any longer.

The following day, PCSACC/400 may be installed without problems , then, all exit programs can be registered again via option 1 and program PCSNETA can be ended without execution of specified workmanagement actions.

Then, another IPL will be performed. You will now have no access protection for one day.

No DDM connection and no user of an exit Programm may be active.

Please check by using commands

WRKOBJLCK QSYS/QPCS *LIB

and

WRKOBJLCK QPCS/PCUSER *FILE.

Step 5: Installation Procedure

Please sign on as QSECOFR or as a user with class *SECOFR . Group profil QSECOFR is not sufficient for the installation process.

Second time installation = installing a higher version of PCSACC/400. In case library QPCS and user QPCS are already existing on the system a second installation is assumed. All your existing data and license number will then be preserved. During the installation your library QPCS will be renamed into QPCSO, an existing library QPCSO will be deleted. All data of library QPCSO will be integrated into library QPCS and adapted.

If library QPCS cannot be assigned, installation can not be performed. The job will be cancelled with an appropriate message.

Step 5a: Installation via Internet (*SAVF)

1. Create a savefile QPCS using command CRTSAVF QGPL/QPCS in the OS/400 library QGPL.

Savefile QGPL/QPCS was created.

2. Sign on to AS/400 via FTP from your DOS-window or using the run option. Switch to binary mode with BINARY. Write the PC file into the savefile QPCS by using PUT.

Savefile QPCS copied via FTP into savefile QGPL/QPCS.

3. Delete old version of program PCSINST
DLTPGM QGPL/PCSINST

4. Restore program PCSINST into library QGPL by using the following command:
RSTOBJ OBJ(PCSINST) SAVLIB(QPCS) DEV(*SAVF) OBJTYPE(*PGM)
SAVF(QGPL/QPCS) RSTLIB(QGPL).

Programm PCSINST restored into library QGPL.

5. Call the installation program by using command

CALL QGPL/PCSINST '*SAVF'

Installation from savefile

Step 5b: Installation from CD-rom

Please mount the cd rom in the optical device OPT01 (Please wait some seconds) and start installation process by using the command LODRUN and specifying OPT01.

The system automatically restores the installation program PCSINST from cd rom for execution.

Step 5: Installation procedure

The complete installation process will be performed automatically without any further user intervention. Informational messages appear during installation process and completion message will be displayed.

Please, under no circumstances, interrupt the installation, CPYF may need longer!

In case of termination (device read error) you can rename the library QPCSO* with the commands

DLTLIB QPCS if the library exist and
RNMOBJ OBJ(QSYS/QPCSO) OBJTYPE(*LIB) NEWOBJ(QPCS)
and if libraries QPCS2924, QPCS2929 and QPCS2939 exist
DLTLIB QPCS2924, DLTLIB QPCS2929 and DLTLIB QPCS2939 and then
RNMOBJ OBJ(QSYS/QPCSO2924) OBJTYPE(*LIB) NEWOBJ(QPCS2924)
RNMOBJ OBJ(QSYS/QPCSO2929) OBJTYPE(*LIB) NEWOBJ(QPCS2929)
RNMOBJ OBJ(QSYS/QPCSO2939) OBJTYPE(*LIB) NEWOBJ(QPCS2939)

If CPYF of protocol data takes too much time, because you forgot to delete the protocol data,
the installation process can be interrupted.

------------------------------------------------Finishing interrupted installation-------------------------------------------------------------------
Now protocol Data in library QPCSO can be removed with commands
CLRPFM FILE(QPCSO/PCOUT)
CLRPFM FILE(QPCSO/PCOUT2)

Attention: Program PCSINST3 clears files in library QPCS and copies them out of library QPCSO. Library QPCSO has to exist.

If installation has been cancelled, it can be completed with
CALL QPCS/PCSINST3 'PCSACC'
CALL QPCS/PCSINST4 'PCSACC'
-----------------------------------------------Now you have finished the interrupted installation successfully--------------------------

Installation is now completed succesfully. There is no more work to do.

Now, make sure that Your data exist, by calling CHGPCS and option 5.

If not alle CPYF commands are successfully executed, you can repeat this process as often as you need with
CALL QPCS/PCSINST3 'PCSACC' and RCLRSC.

Then, libraries QPCSO, QPCSO2924, QPCSO2929 and QPCSO2939 may be deleted, they are containing Your previous data.

Please, keep the installation protocol, file QPSRLDSP contains informations about installed objects and the printed joblog.

Step 7: Restart Workmanagement jobs for exit programs
(USRPRF *SECOFR or QPCS only)

Call the program to activate the exit programs via command PCSNETA or in command CHGPCS via option 01.

F10 should be used to receive the display of workmanagement functions to be started. The necessary actions can be selected via F2 and have to be confirmed again via F2. After processing the Start jobs, You are now again ready for production.

Restart of workmanagement jobs may be performed via IPL or restart from restricted mode, e.g. following a daily save operation. Or later on from the system console. Function F10 for restart from command PCSNETA should be used for this.

Step 8: Automation of important tasks with ADDJOBSCDE

Call command CHGPCS, use option 03 to call the maintenance program for working with job scheduler entries. ADDJOBSCDE and WRKJOBSCDE are possible.

The following jobs have to be on the system

Option 10: Automatic conversion of log data daily. Use command CVTPCSLOG in order to
automatically convert logged access data into access authorities, e.g. Once a day. That way you will receive an actual status about your system automatically.

Option 11: Print disk space utilization once a week via command PRTSPC. That way you will receive a weekly overview about the disk utilization of PCSACC/400.

Option 12: Adopt user profile descrioptions daily via command GETUSRTXT.

Option 13: Remove deleted user profiles daily from PCSACC/400 via command CHKUSRPRF.

Option 14: Deletion of log entries during normal operations. Command CLRPCSLOG should
be run prior to an IPL. Deletion should not be activated in command RGZPCS.
back to top

Step 9: Customization - change JOBQ, OUTQ and print format.

From command CHGPCS, use option 2 to call the maintenance program for PCSACC/400. The values can there be adjusted.

Additional text for error messages has been adjusted and the printing values have been changed.

On this page, assignment of application authorities, adjust IFS accesses.

These values are important for conversion of log data into access authorities. Value '1' should be used for individual application authorities.

Additionally, access may be rejected to QSYS.LIB via Windows NetServer for all users.You may control, whether a user needs to be registered within PCSACC/400 , if he only is being using the Update function of iSeries Access for Windows.

On this page, You may control if automatic correction of user authorities shall be performed.

Problem - A user is member of a user group and does not have own data authorities.
If now recorded log data are being converted via option S, the user will receive own data authorities. To have access to this data authorities, the user has to be entered into the list of groups.
If the user is stored as a group and all data rights will be removed, the group will be corrected as well and the user name will be deleated.

With these system values, the correction will always be performed automatically.

An error message will be sent to QSYSOPR if there´s an FTP-access taking place and the user is not registered within PCSACC/400 and no user profil is existing within i5/OS.

With these system values you can manage if a message should occur, where the message should be sent, the language of this error message and if the password should be included within this message.

Furthermore you can switch off ANONYMOUS-Support generally.

If the user text will be changed in PCSACC/400, user text will be changed in the i5/OS user profil as well. If the library-, file-, data queue-, data area and member text will be changed, these descriptions will be adopted to all records with the same key. I5/OS objects will be changed as well.

These functions can be switched off totally or partly by using these system values.

If the TELNET exit programs have also been activated, the above values have to be adjusted.

These values are important, if startup of TCP/IP runs concurrent to the command RGZMASTER called from program QSTRUP.

Step 10: Register in PCSACC/400 as administrator
(USRPRF QSECOFR or QPCS only)

Call command ADDPCSOWN and specify the name of your user profile.You are now administrator of PCSACC/400. User QSECOFR and QPCS are owner and administrator of PCSACC/400 by progam.

Miscellaneous information

Size of log files

As all users are activated in test mode and logged data are converted into access authorities daily via command CVTPCSLOG, log files remain very small.

Save library

Library QPCS will not be saved when performing save of all user libraries (SAVLIB *ALLUSR). It has to be added to the save procedure seperately.

Reorganization

Topic 'Reorganization' will be covered by a separate entry in 1. help. http://www.pcsacc400.com/first.htm

Problem: some user profiles cannot be controlled by PCSACC/400

If user profiles exist whose activities do not appear in PCSACC/400 and new user profiles are working correctly, then old user profiles from OS/400 V2 are being used. Please delete these old user profiles using command DLTUSRPRF and create new user profiles with command CRTUSRPRF. Own authorities can be stored with an intermediate user profile. This is the only possible way to solve that problem and is recommended by Rochester.

Defect/non-defect support

Should you have any problems or questions, please send a fax to: Busch & Partners 0049 (0) 4163 812828 or an E-mail to Busch@pcsacc400.de describing your problem or question.

In urgent cases you may directly call 0049 (0) 4163 811771 Busch & Partners.
In case nobody can be reached, you may call cellphone number 0049 (0) 171 222 8689 with an mail box.

Ending of test period (only test versions with time limitations)

The interface programs can be deactivated by using command PCSNETA.

After expiration of test period the maintenance program CHGPCS can no longer be used. The interface programs will terminate controlling, log records will no longer be created and all users can proceed operations without any limitations. An error message will be sent to QSYSOPR once daily.

Caution: Sub exit programs will no longer be supported.

If you are working with sub exit programs, active exit programs must be deactivated via command PCSNETA.