PCSACC/400 First 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 i5/OS V6R1.
Please follow the attached Ptf informations.

For security level 40 the libraries QPCS, QPCS2924, QPCS2929 and QPCS2939 must be added to the system value QALWUSRDMN, if this values is not set to *ALL.

Warning: This programs are copyright. For installation a unique license number for your system is required, LPAR partition number is part of the license key. This number will be delivered with the Programm or send via email.

Step 2: Installation Procedure

Time for installation will take appr. 10 minutes or less.
Please sign on as QSECOFR or as a user with class *SECOFR . Group profil QSECOFR is not sufficient for the installation process. The RSTLIB function allows installation during current system operations.
The exit programs always have to be activated manually.

Step 3a: 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.

 back to top

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.

 back to top

3. 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.

 back to top

4. Call the installation program by using command

CALL QGPL/PCSINST '*SAVF'

Installation from savefile

 back to top

Step 3b: 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.

 back to top

Step 4: 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. At installation time the language is allocated dependend on the primary language, german 2929, german international 2939 and us english 2924 are supported.

Installation is now completed succesfully.

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

Not only libraries QPCS, QPCS2924, QPCS2929 and QPCS2939 have been created, but also userprofiles QPCSand QPCSIFS and commands ADDPCSOWN, ADDPCSKEY. CHGPCS, CHKUSRPRF, CLRPCSLOG, CVTPCSLOG, CPYUSR, DSPCOPY, GETUSRTXT, PCSNETA, PRTLOG, PRTPCS, PRTSPC, PRTUSR, RGZSET, RGZPCS and RGZMASTER are copied in library QGPL.

 back to top

Step 5: Further actions after installation

The password of user QPCS should be changed now.

The user profile QPCS is member of the class *SECOFR.

The name QPCS for user profile and library is reserved from rochester for PCSACC/400. It is not necessary to add library QPCS to system value QUSRLIBL.

 back to top

Step 6: Required OS/400 Ptf's:

Please have attention also to ptf informations and tips.

Required Ptf's have to be installed and applied prior to activation of interface programs.

 back to top

Step 7: 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.

 back to top

Step 8: Call maintenance program CHGPCS

Signon with your name and call command CHGPCS.

You can find important information on the above screen. Entering 1 prevents further display of this screen.

 back to top

This command is the main command for maintenance of PCSACC/400 - all functions have to be executed via this command.

 back to top

Step 9: Important notes before the activation of the exit programs

For first use of TCP/IP TELNET - user exit programs, read chapter 6 in the online documentation first. Do not activate Telnet interface programs if you are exclusively using DHCP for IP address assignment.

System value QRMTSIGN
After activation of TELNET exit programs, the system value QRMTSIGN e.g. with value *FRCSIGNON will no longer be checked. The field for Auto-Signon in the TELNET IP address file of CHGPCS has to contain value 0 in the default record '*.*.*.*'. This even is required, if the system value for TELNET control in PCSACC/400 still is set to 1 = no TELNET control.

 back to top

Step 10: Call activation of the exit programs

For activation of the exit programs use command PCSNETA.

If you want to restart the workmanagement jobs from Programm PCSNETA after activation of the exit programs and TCP/IP TELNET5250 also is selected, PCSNETA has to be called from the system console.

 back to top

If no active exit programs are being displayed, activation can be performed without any problems.

In most cases, TFTP as well as TELNET5250 will not be activated at first activation.

Via option 1 the interface programs that have to be activated can be selected.Changes will be executed by pressing the enter key.

Now the workmanagement jobs have to be restarted. SQL/ODBC-, FTP- and DDM accesses will immediately be controlled. For controlling of hostserver jobs, remote commands, data queues and netserver, restart of displayed workmanagement jobs is mandatory.

An IPL serves the same purpose.

 back to top

Execution of required functions via command key F2.

Via F2, the displayed operations will be executed. A confirmation window will be displayed and the final execution has to be confirmed via F2. After execution of all jobs there will be a 30 second wait time.

 back to top

Now the start menu will be displayed.

Via F2/F2, the displayed jobs will be started. Upon completion there will be a wait time of 20 seconds.

 back to top

Step 11: Automation of important tasks with ADDJOBSCDE

The default setting of PCSACC/400 allows automatic registration of new users and logging of all accesses. No accesses will be rejected, all users can proceed operations without limitations. Eventually Existing interface programs can still be used as subexit programs.

New users will be assigned to group QNEW and can easily be identified on the entry menu. QNEW is being identified by the exit programs as marking entry.

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

 back to top

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.

 back to top

Step 12: 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.

 back to to

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.

 back to top

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.

 back to top

Step 13: First steps after installation - how to work with PCSACC/400

All maintenance functions can be performed using command CHGPCS.

Online guidance: Detailed, field sensitive help functions are available for all fields within the security database. Positioning the cursor to the appropriate field and pressing the help key will give you all necessary guidance.


As administrator *ADMIN, controller *CONTR or main security officer *SECOFR, You may display the documentation via option 30 from CHGPCS.

The first row contains a users guide that may be printed.

This manual especially should be used to become familar with the application and to understand the following important functions:

- actions after installation, performance tips
- frequently asked questions and answers
- creating authority data structures
- existing commands, programs, changing printer files

It is recommended to gather experience with the application as test user and to activate authorithy for a single user only.

All other users will automatically be registered, access data will be logged and converted daily into access authorities by using command CVTPCSLOG.

The documentation contains links to all pages of documentation on the homepage - they may only be called from a 5250 session.

 back to top

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.

 back to top