FAQ

How do i turn a filejob in OPRS into a prestart job?

How do i turn a filejob in OPRS into a prestart job?

BUREPFJB

 

This command is used to convert a filejob in OPRS, to a PJ in the PDSOPRS subsystem.

Use F4 to initate a command prompt, using the default values usually works just fine.

The benefit of always using PJ instead of a scheduled job, is that when the server has been down for backup/IPL/Maintainance, all the necessary jobs in the PDSOPRS subsystem will be started automatically.

How do i use OPRS to change to summertime/wintertime?

How do i use OPRS to change to summertime/wintertime?

The recommended way to change from wintertime to summertime is manually as follows:
-  Change the execution time for jobs scheduled with in the next hour  if needed.
GO PJOB
Select option 2="Work with scheduled jobs"
-  Stop applications
-  Make sure no important jobs are running in the OPRS subsystem
WRKACTJOB
- Stop the OPRS subsystem
ENDSBS   PDSOPRS   *IMMED
- Change the system value
WRKSYSVAL   QHOUR
Use Option 2=Change to set the system time
-  Start the OPRS subsystem
STRSBS   PDSOPRS
Note: Many applications and servers (such as Domino servers) may also need to be stopped while changing the system time.


Another solution is to schedule a file job containing the following commands:
Filejob SUMMERTIME:
CHGSYSVAL SYSVAL(QHOUR) VALUE('03')
ENDPJ  PDSOPRS  BUBMUPR  *IMMED
DLYJOB 15
STRPJ  PDSOPRS  BUBMUPR
Use the following attributes when scheduling the job:
Time for execution:                0201
Text                                Change to summer time
Sequence                        8 = Once
First execution:                30/03/07   Sunday
Command:                        PEXCFILJOB  SUMMERTIME
Job (on page 2):                SUMMERTIME
You may also need to change the execution time for jobs scheduled between 0201 to 0305 on sunday.
GO PJOB
Select option 2="Work with scheduled jobs"

What is new in version 9 of OPRS?

What is new in version 9 of OPRS?

Release 9.0 is the second newest release of OPRS. You will find that a lot of new functions have been added. For the newest version of OPRS, look for Whats new on release 9.3 of OPRS.

This document covers the most important changes made in this release.

Job scheduling

The maximum command length has been increased from 200 to 1000 characters. This may reduce the need to write your own programs for complex CL commands.

Parameter “Job queue”, “Output queue” and “Message queue” may now be qualified by a library name. The library names are defaulted to *LIBL.

A new calendar file has been added. This allows you to specify from and to dates and time where all or selected jobs should not be submitted. A typical use for this function is when planning for holidays. A new menu option to work with calendar item has been added to the PJOB menu.

The “Work with scheduled jobs” function has been changed. Use the F11 to display alternative information about the jobs. A new status column display the makes it easier to determine which jobs that will not be started. E.g. The status will be displayed as “Held” in blue color, while job held due to a calendar entry will be displayed as “Calendar” in pink color. In the previous display the hold status was   indicated with a single “Y” next to the job text.

The “Work with executed jobs” function has been changed. Use the F11 to display alternative information about the jobs. A new status column display the makes it easier to determine the current status for the jobs and if the jobs completed normally or not. Also it has become easier to see if a job has expired or if error was detected when trying to start a job. The job status may be one of the following:

  • · Message waiting (Color = Pink)
  • · *Active (Held) (Color = White)
  • · *Active (Color = Pink)
  • · Job on inactive job queue (Color = Pink)
  • · Job held on job queue  (Color = Pink)
  • · Job on held job queue  (Color = Pink)
  • · Job on job queue  (Color = Pink)
  • · *Unknown job status
  • · Completed normally
  • · Cancelled on job queue  (Color = Red )
  • · Job ended abnormally  (Color = Red )
  • · Held  (Color = Blue)
  • · Job expired  (Color = Red )
  • · Error on submit job  (Color = Red )

Some new parameters make it easier to schedule a job to be started in a fixed interval throughout the day, e.g. every ten minutes.  The following parameters are involved:

  • · Repeating job  (yes or no)
  • · Repeating job interval in minutes
  • · End time for the

The next execution time is calculated after a repeating job has been started. This reduces the number of entries found in the “Work with scheduled job” display.

New maintenance fields have been added to make it easier to se the name of the job and user who created the job and when the last change was made.

File jobs

Maintenance fields have been added to all files involved. It makes it easier to track who and when someone last edited a file job or an entry in it.

A new “Description” field allows you to enter your own description for CL commands and save commands.

More options have been added for the save function in file jobs.

A new command allows you to verify if the correct tape has been mounted for the upcoming backup job.

The “Work with” function for CL commands has been improved. You may change several commands on the same time, which makes it easier to use the Copy/Paste function more efficiently. Also you may like the new “Window” function which allows you to “roll” the commands sideways.

The implementation for the “Run in test mode” parameter has been changed. If this parameter is set to *YES, then file job operations such as executing a CL command will not be performed. Instead a message will be sent to the job log.

Job history

The file size is no longer limited by the job number. This allows you to store job history for important jobs longer.

The job history lists are a function that allows you to extract information for a subset of jobs in an easy way. The time limit parameter for the Retrieve Job List (PRTVJOBLST) command is no longer required, which allow you to process all information in the job history file.

Backup

A new menu option on the PSAVE menu allows you to edit the file jobs used for backups.

Other minor changes:

  • · Support for keyword SAVACT has been added for the Save Change Object command
  • ·
  • · d *IBM
  • · Wrong number of parameter when calling program “Work with objects for restore” has been corrected

Use the new Document Restore Job (PROCRSTJOB) command to document restore commands for a backup job or part of a backup job, e.g. the daily backup job.  The restore procedure is based on the information in the "Saved objects" file in OPRS, also known as BUF502. The output from this command is either a text file or a CL program.  The text file may easily be viewed from a PC using Notepad or Wordpad.  If output is said to be a CL program, you will have an easy way to run all restore commands. The default name is BURSTxxx where "xxx" denotes the weekday, e.g. BURSTWED.

Job groups

The Job Group function allows you to create and run a list of jobs grouped together by a group name.  Each job may have individual parameters such as job name, job queue etc. When a job group is started, the jobs in the group will be submitted in a controlled manner. When the first job ends, the next one is submitted and so on. A recovery job may be specified to run if one of the jobs in the group ends abnormally. The remaining jobs in these cases will not be submitted.

The changes in this release are:

The job group function has been changed to avoid any restrictions regarding duplicate job numbers. New maintenance fields have been added to make it easier to se the name of the job and user profile who created the job and when the last change was made.

When you start a job group, the job group entries will be copied to a separate file. This allows you to make changes to the job group without influencing the currently active job group. Results from any job dependency checking is also stored in a separate file, which makes it much easier to find out which dependencies were validated true or and which were validated false.

A new option has been added to the “Work with status” display. You may now display the last result from an event validation. Another new option allows you to display the job history for a job.

More options have been added to the “Work with status for job group” display. You may now display the result from a dependency validation for a job group entry.

When you press F11=“Display status” on the “Work with job groups” display, the completion code will now be displayed in red color for job groups that ended abnormally.

Configuration monitoring

This function may be used to monitor configuration objects, such as lines and controllers, to see if they have the normal status. Optionally you may specify actions to be made if an object does not have the desired status to try to make it become normal again.

In this release, several new options have been added to the “Work with configuration objects to be monitored”. One option allows you to work with the current status for an object. Another new function allows you to retrieve a list of all active lines. Another new option gives you an easy way to work with From/To times for the monitoring.

Two new commands allow you to merge or subtract monitoring lists. The Merge Monitoring List (PMRGMONLST) command may be used to merge to monitoring entries from one list into another. Use the Subtract Monitoring List (PSUBMONLST) command to subtract a monitoring list from another list. See the help text for the commands for more information.

Use the new Execute Commands for Configuration Monitoring list (PEXCCFGLST) command to execute CL commands for objects in the monitoring list. Only entries with an abnormal status will be selected, however this might be overridden.

Use the new Retrieve Ping Statistics (PPINGSTAT) command to verify connection to a TCP/IP connection and collect information to a database file. The main purpose with this function is to be able to verify the connection quality.

Job monitoring

This function may be used to monitor the active jobs and subsystem to see if all the desired jobs are up and running. Optionally you may specify an action to be made if a job does not have the desired status to try to make it become normal again.

In this release, several new options have been added to the “Work with jobs to monitor” display. Use option 7=History to work with job history for a monitored job. Use option 9=“Work with” to work with the monitored job. Use the new “Work with from/tom times“ function to work with when monitoring should be active for the individual jobs. A new “Position to” field have been added which allows you to positioning the display to a specific subsystem.

Several new options have been added to the “Work with job status” display. Use option 7=History to work with job history for a monitored job. Use option 9=“Work with” to work with the monitored job. A new function key option allows add a job to be monitored. Another new function key compares the monitoring list against the information in the Job History file. A new “Position to” field have been added which allows you to positioning the display to a specific subsystem. Option F6=Add has also been added. Use the new “Work with from/tom times“ function to work with when monitoring should be active for the individual jobs.

Two new commands allow you to merge or subtract monitoring lists. The Merge Monitoring List (PMRGMONLST) command may be used to merge to monitoring entries from one list into another. Use the Subtract Monitoring List (PSUBMONLST) command to subtract a monitoring list from another list. See the help text for the commands for more information.

Use the new Execute Commands for Job Monitoring list (PEXCJBMLST) command to execute CL commands for jobs in the job monitoring list. Only jobs with an abnormal status will be selected, however this might be overridden. The main purpose for the command is have to an easy way to notify the operator by sending GSM text messages (SMS) for jobs that do not have the desired status.

Use the new Add jobs to monitor (PADDJOBMON) command to add a list of active jobs to the list of jobs being monitored. Jobs may be selecting by using Job, User and/or Job type as subset criterion.

Message monitoring

In the previous release an error message would occur if a message file was deleted while still having messages in the system operators message queue (QSYSOPR). This has been corrected.

Error in function “Work with message action” corrected when trying to specify selection for message data.

A new function allows you to remove old inquiry messages from the system operators message queue. I.e. these are inquiry message that have not been replied to, but the job that sent the message is no longer active.

When monitoring for inquiry messages in QSYSOPR, you may now ignore selected inquiry messages in QSYSOPR. This allows you to acknowledge a message and have OPRS detect any new ones.

The message center function is an alternative way to work with messages in QSYSOPR. Changes:  When an invalid reply is entered, the message status will still be “Active”.  Also, the message will remain as “Active” if an error is encountered when a command is executed.

The message monitor may now be run as a prestart job in the OPRS subsystem. I.e. the message monitor function is started as soon as you start the OPRS subsystem.

User defined menus

The User Defines Menus function gives you an easy way to create and maintain menus used to run the daily operations.

In release 9.0 the “Work with” functions has been improved. You may change several commands on the same time, which makes it easier to use the Copy/Paste function more efficiently. Also you may like the new “Window” function which allows you to “roll” the command sideways.

Use the new Display Journal Attributes (PDSPJRNA) command to display the total size for all receivers attached to journals.

System monitor

The system monitor function has been improved. More monitoring functions have been added, and it is our intention to keep rolling out new monitoring functions as soon as possible. They can be downloaded from our web-site.

A new comment file has been added. A comment may be added for all systems, a specific system or a condition.

Monitoring intervals, From/To times, may be specified for each system.

When monitoring for inquiry messages in QSYSOPR, you may now ignore selected inquiry messages in QSYSOPR. This allows you to acknowledge a message and have OPRS detect any new ones.

The Check ECS connection (PCHKECS) command is a new function.  Use this command to test the communications link to your service provider by using the The Send Service Request (SNDSRVRQS) command. You may specify the name of a system condition to be set according to the result of the verification. You may also specify commands to be executed if the verification ends in error or not.

The Check FTP log (PCHKFTPLOG) is a new function.  Use this function to verify that the requested number of put, get and remote command has completed normally during a FTP session.

You may specify the name of a system condition to be set according to the result of the verification.

The Check for messages not sent (PCHKGSMTXT) command is a new function. Use this function to verify that there are no SMS messages waiting in queue for to be sent. Du may specify a time limit for the messages. The default time limit is 5 minutes. You may specify the name of a system condition to be set according to the result of the verification.

Use the new Check if new Library/Directory (PCHKNEWLIB) command to monitor if a new library or a new folder in the root directory has been created.  Background: Many installations are running High Availability software such as VISION to mirror data from one system to another. If someone is creating a new library or directory, you may need to update the parameters in the mirroring software to include the new library or directory in the mirroring process.

The new Check SST User id and Password (PCHKSSTPWD) command may be used to verify if a SST password is still valid.

The new Check status for virtual devices (PCHKVRTDSP) command to see there are a number of available virtual devices.  You may either specify the number of devices to check as a number or as a percentage of the total number of virtual devices found. The following limits may be specified:

  • · The minimum number of devices expected to be varied on
  • · The maximum number of devices expected to be varied off
  • · The maximum number of devices expected to have another status

The new Check number of output queue entries (PCHKOUTQS) command is intended to replace the old PCHKOUTQ command. Use the command to verify if the spooled files in the output queues are at a normal level and/or the queue status is normal.

Other functions

Execute Active Job (PEXCACTJOB) command

The PEXCACTJOB command processes CL commands for selected active jobs. More than one command may be specified to be executed for each entry. Substitution variables may be specified which will be replaced with the subsystem name, job name, user name or the job number.

In release 9.0 some new parameters have been added. They allow you to process jobs depending on how long time the jobs have been active. A typical example of use: If a user does not sign off the application in a controlled matter, some server jobs may still be active. The PEXCACTJOB command may be used to end active server jobs if they have been active for more than 36 hours.

A new parameter has been added to be able to select jobs by using the current user. The current user specifies the profile under which the initial thread is running. For jobs that swap user profiles, this user profile name and the user portion of the job name can be different.

Another new parameter has been added to be able to select jobs by testing for the current temporary storage used. The temporary storage is used for storage required by the program itself and by implicitly created internal system objects used to support the routing step.  If the maximum temporary storage is exceeded, the job is ended.  This does not apply to the use of permanent storage, which is controlled through the user profile. This parameter may help you to locate jobs that are using a lot of disk space. There have been a lot of situations where the percentage of auxiliary storage used is increasing rapidly together with the "Temporary storage used" value from the Work with System Status display.

The Retrieve Active Jobs (PRTVACTJOB) command has been changed and is now using APIs to retrieve the list of active jobs. The output file generated has been extended to also include the following fields:

  • · Temporary storage
  • · Current user profile

Note 1: The RESET parameter on PRTVACTJOB is now working slightly different than in the previous release. The CPU percentage used will now always be calculated based on the time interval since the previous execution of the PRTVACTJOB in the current job. The Response times for the jobs will be the average since the interactive jobs started. The Auxiliary I/O will be calculated  from the previous PRTVACTJOB command with RESET(*YES) parameter.

Note 2: The changes in the PRTVACTJOB have also caused some changes in the PCHKLOOP command.

Execute Object List (PEXCOBJLST) command

A new parameter on the Execute Object List (PEXCOBJLST) command allows you to select objects depending on the number of days since the object was created, last changed or last used.

Example: The PEXCOBJLST is used to delete log files 14 days after creation.

Display Job Log (PDSPJOBLOG) command

This function interprets the content of a spooled job log and makes it easier to read. The information displays have been improved. The command may also be used to view the job long for active job. A new field has been added allowing you to reply to any inquiry message in QSYSOPR directly from the screen. Also a new Reload function key has been added.

Print Disk Information (PPRTDSKINF) command

The previous release had a limit of  9.999.999.999 bytes, i.e. approximately 10GB, for a single object. In this release the maximum size for an object has been increased to approximately 1000.000 GB. We will continue to increase the maximum limit, but we assume that this will not be necessary the next couple of years.

Also, a new parameter allows you store the reports as text files in the Integrated File System. The default directory is “/OPRS/Diskinfo_ReorgStatus.txt“. The program will no longer stop if files without any data members are encountered.

Maximum number of libraries in the library list

All initial programs have been change to allow for more than 25 libraries in the jobs library list.

Start TCP/IP File Transfer (PFTP) command

Use this command to start a FTP session where the FTP commands are stored in a source member. This reduces the need to write your own CL programs.

Optionally you may specify that to start the Source Editing Utility to edit the FTP source member.

You may specify the name of a system condition to be set depending  on how the FTP session ends, i.e. A condition will be set to *NORMAL if an object is found, otherwise the condition will be set to *WARNING. You may also specify commands to be executed if the verification ends in error or not.

Use the ANZLOG parameter to display the FTP log where successful commands are shown in green and unsuccessful command is shown in red color which makes it much easier to read the log.

Change owner for a library and it objects (PCHGLIBOWN) command

This is a new function. Use this command to change owner for a library and it objects

Check active subsystems (PCHKACTSBS)

This is a new function. Use this command to verify that all subsystems have been started and to see if there are any new active subsystems.

The command may be run in the following modes:

  • · Check subsystem status
  • · Display subsystems in error
  • · Work with subsystems to monitor
  • · Prepare for PCHKACTSBS

Display Directory Sizes (PDSPDIRSIZ) command

This is a new function. Use this command to display the total size for all directories in the root directory in the integrated file system. The information is based on the Retrieve IFS Size (PRTVIFSSIZ) command. We recommend that you run this command daily.

Historical information will be kept and may be displayed.  This makes it easy to see how the total size for a specific directory has grown.

By default the sizes for the following directories will not be retrieved:

  • ·
  • · QDLS

Display Link (PDSPLNK) command

This is a new function.

The Display Object Link (PDSPLNK) command shows a list of names of specified objects in directories and their sizes.

It is also easy to run restore commands just by typing an option in front of an object name. Use the Job Queue parameter (JOBQ) to control whether the restore should be run in batch or interactive.

Use the Restore Directory (RSTDIR) parameter to specify if the restore should be made to the originally directory or to another.

You may only select up to 20 objects to be restored at one time.

Any restore command will always be prompted.

Print Reorganization status (PPRTRGZSTS) command

The PPRTRGZSTS is used to print the current reorganization status  for a single library or for all user libraries, i.e. if there are any files with an excessive number of deleted records.

In release 9.0 a new parameter allows you store the report as a text file in the Integrated File System. The default file name and location is: “/OPRS/Diskinfo_ReorgStatus.txt'“. Also, the program will no longer stop if files without any data members are encountered.

Print Record Capacity status (PPRTRGZSTS) command

This command may be used to print the maximum file capacity for all user libraries or a single library. It is usually used to locate files there are in danger of getting full. I.e. avoid messages such as "File XX is full (C I)".

In release 9.0 the program will no longer stop if files without any data members are encountered.

Monitor Output Queue (PMONOUTQ2) command

This is a new command.

This command may be used to monitor an output queue and have the spooled files placed on the queue to be automatically converted to text files in the integrated file system (IFS). Optionally you may also transfer the text files to another system using FTP.

Repeat execution of CL command (PREPCMD) command

This is a new command.

Use this function to repeat execution of a CL command. You need to specify a CL command and a delay time between each execution.

The CL command will be executed either:

- A number of times

- Until a specified ending time has been passed

- Depending on if an error message was received or not

Example

The PREPCMD is used to start a subsystem. If an error message is received for the Start Subsystem (STRSBS) command, the program will wait for 10 seconds and try to run the STRSBS command again. This will be repeated every 10 seconds for 15 minutes. (6 retries = 1 minute, 15 * 6 = 90 retries = 15 minutes) Command execution will end if no error message is received.

PREPCMD CMD('strsbs PDSOPRS') DLY(10) NBR(90) QUIT(*IFNORMAL)

End Domino server (PENDDOMSVR) command

This is a new command.

Use this command to stop a Domino server and wait for the server jobs to end. The command may run the following options in order to stop the server jobs:

- Stop the domino server controlled using OPTION(*CNTRLD)

- Stop the domino server immediate using OPTION(*IMMED)

- Stop the domino server jobs using the ENDJOBABN command

For each option you may specify a number of minutes to wait to allow the option to complete.

You may also specify a CL command to run if a step is not successful.

Retrieve program references (PRTVPGMREF) command

The Retrieve Program References command retrieve information for some or all programs in a library.

Use the “Work with program references” on the PWRK2 menu to display the result. This function gives you a better view of the program references than the output from the OS/400 command DSPPGMREF.

In release 9.0 a new function has been added which allows you to display object usage and compare creation dates and times between the program and the object being referenced. Also, new fields for object creation date and time and program creation date and time have been added to the data base file. This makes it easier to e.g. locate program that need to be recompiled after you have recreated some files.

Work with output queue (PWRKOUTQ) command

The Work with output queue command no longer support *ALL as the output queue name. Use the new command PWRKOUTQS for this purpose.

Work with output queues (PWRKOUTQS) command

This is a new command.

Use this command to work with the current status for output queues with options to set up monitoring parameters such as maximum number of output queue entries and normal status.

The Check Output Queues (PCHKOUTQS) command is used to verify if the spooled  files in the output queues are at a normal level and/or the queue status is normal.

Example: A typical scenario may be:

   QEZJOBLOG - Less than 5000 job logs

   PRT01 - Less than 50 files

   QPRINT - Less than 200 files

   any other queue - less than 100 files

Check number of output queue entries (PCHKOUTQS) command

This is a new command. It is intended to replace the old PCHKOUTQ command

The Check Output Queues command is used to verify if the spooled files in the output queues are at a normal level and/or the queue status is normal.

See the online help text for PWRKOUTQS command for more information.

How do i hold jobs in a particular time period?

How do i hold jobs in a particular time period?

You will need version 9 of OPRS to use this function. You can find the version number on the top of the main menu in OPRS. Contact us for the latest version if you have an older version.

If you are going away on a holiday, or running some maintenance on the system in a weekend, you can use the function “Calendar Entries” to prevent jobs from being run in that particular period of time. Instead of using the job scheduler “hold” function for each and every job, you will find the “Calendar Entries” much easier to use.

Here is what you do:

If you want all the jobs in a period of time to be held, skip the next section. If only certain types of jobs are to be held, and you already have given them a 3 digit code in the job scheduler, you will need to register that code in the “Calendar Entries” system.

Say your report jobs are categorized in the job scheduler with the code “REP”. Now you need to register the code “REP” in the “Calendar Entries” system. This is what you do:

From the main menu of OPRS, choose menu option 4: Job Scheduling Menu, and then choose menu option 8: Work with group codes and authorization. Hit F6 to add a new group, call it “REP”, and enter a description for it, for instance “My Report Jobs”

At this point, you either have a valid group code for the jobs you would like to hold, or you just want all jobs to be held for a period of time. The next thing you need to do is specify the from and to dates. On the Job Scheduling Menu, choose menu option 9: Work with calendar entries. Hit F6 to add a new interval of time. Enter *ALL in the first field if you want all jobs in that time period to be held, or the code “REP” that you registered earlier if for instance only your report jobs are to be held. Then specify from and to date, and you are done.

To confirm what jobs are being affected, choose menu option 2: Work with scheduled jobs and on the right-hand side of the screen you will see the text “Calend” on the jobs that are being held due to an entry in the “Calendar Entries” system.

Note: When you schedule jobs, you have the option to specify whether a job should be affected by the “Calendar Entries” system or not. You will see a parameter that can be set to “Y” or “N”, like this: Hold on calendar days    Y          Y=Yes, N=No

If you choose “N” here, this job will not be held even if it qualifies by *ALL or group name.

How can i locate scheduled jobs with a certain output queue?

How can i locate scheduled jobs with a certain output queue?

You may use F10=Subset from from the "Work with jobs to schedule" display to search for jobs with a certain job name, job queue and etc. However, "Output Queue" is not one of the fields available on the "Subset jobs" display. Instead you can use Query to display information in the file.

E.g. :   Runqry   *none   BUBSREP  rcdslt(*yes)

Files that could be of interrest:

BUBSREP - Jobs to schedule

BUA9REP - File jobs

BUCAREP - Scheduled jobs

In addition you may use the "Work with job parameters" on the PPARM menu to verify output queues used by OPRS.

PPRTDSKINF - how to omit library from "possible old, test or temp. objects report.

PPRTDSKINF - how to omit library from "possible old, test or temp. objects report.

The selection criteria is stored in a message. Use the following command to work with the message description:

Wrkmsgd  OPR0326  BUOPMSG

The message looks this:

Message:

Query selection to be made when looking for temporary,
test or old versions of objects. Enter selection as Second level text.

Second Level message:

ODOBNM *eq %wldcrd("*TEMP*") *or ODOBNM *eq %wldcrd("*tmp*") *or ODOBNM *EQ
%wldcrd("*TEST*") *or ODOBNM *eq %wldcrd("*TST*") *or ODOBNM *eq        
%wldcrd("*001") *or ODOBNM *eq %wldcrd("*OLD")

To omit a certain library from the report, you can change the second level text as shown in the example below:

(ODOBNM *eq %wldcrd("*TEMP*") *or ODOBNM *eq %wldcrd("*tmp*") *or ODOBNM *EQ
%wldcrd("*TEST*") *or ODOBNM *eq %wldcrd("*TST*") *or ODOBNM *eq          
%wldcrd("*001") *or ODOBNM *eq %wldcrd("*OLD")
) *and ODLBNM *NE "BUENGGEN"

What is new in version 9.3 of OPRS?

What is new in version 9.3 of OPRS?

Whats new in release 9.3?

This document covers the most important changes made in this release.

Miscellaneous

=======================

A new command Authorization code information (PAUTINFO) may be used to display selected information used to validate the authorization code for OPRS.                  

A new command Remove old Ping statistics (PRMVPNGSTA) removes old PING statistics. This information is retrieved with the PPINGSTAT command.

A new command Compare file field descriptions (PCMPFFD) may be used to compare file field descriptions for two database files.

The Display Program References has been changed to support *LIBL for referenced objects.

The Install OPRS command (PINSTALLIA) may be used to install OPRS in a IASP environment.

Use the Work with OPRS Prestart Job (PWRKOPRSPJ) command to work with all prestart jobs for the OPRS subsystem and the current status.

Use the Display PTF Status (PDSPPTFSTS) to display the current status for PTFs on system regarding status and IPL actions. From this display you may also work with the list of valid status and IPL actions.                                          

Several screens has been optimized for the 27x132 screen size which allows you to display a lot more information on a single screen.          

User options may now be used from the Work with Members (PWRKMBR) screen. This makes it easier to e.g. increase the maximum file size from this screen.

Spooled file management

=======================

A new command has been added, Retrieve OUTQ entries (PRTVOUTQX). The regular PRTVOUTQ has a maximum limit of approximately 100.000 spooled files. This is due to API and User Space limits.                  

The maximum number of entries to be processed with the PEXCOUTQ command has been increased from 99999 entries to 9999999 entries.

The maximum number of message Ids to be ignored on the OPRS Display Job Log (PDSPJOBLOG) command has been increased from 20 to 60. This function is evoked from several OPRS functions such as the Job Scheduler functions and the Job History function.

Backup

======

The function to check if there is enough free space before saving to savefile is now supporting V7R1 of the operating system,

Object management

=================

A new command Analyze IFS entries (PANZIFSE) may be used to analyze the number of IFS entries on the system.

Use the Delete Savefile (PDLTSAVF) command to delete old savefiles. A new parameter SAVF has been added to only process files with a certain name.

Use the new Execute commands for IFS entries (PEXCIFSE) command to process cleanup or other operations for selected files in the Integrated File System (IFS).

Job scheduling

==============

Support for the Country Id (CNTRYID)) on has been added.

The function for converting jobs from the OS/400 Job Scheduler has been enhanced.

A program dump will be produced if OPRS fails to submit a job due to parameter error on the command. This makes it easier to determine what it is actually wrong.

The Check Executed Jobs (PCHKEXCJOB) has been improved to makes it easier to monitor if one or more jobs in the Job Scheduler function ends abnormally.

System monitor

==============

When monitoring more than one system: A default command may be specified when using the 5=Work with" option for a Condition. This is usually used to evoke the TELNET command to log on to a secondary system.

The Check Executed Jobs (PCHKEXCJOB) has been improved to make it easier to monitor if one or more jobs in the Job Scheduler function ends abnormally.

A new command Disk/CPU info remote systems (BXDISKCPU) may be used to retrieve information about Disk CPU usage for a remote system. This is based on DDM file communication.

Messages in the QSYSOPR message queue that requires a reply may be forwarded to a focal point. This is based on DDM file communication.

New programs have been written to make it easier to set up a prestart job for each system being monitored.

A new function retrieves the system date and time for remote systems and displays this on the HTML version of the System monitoring display. The main purpose is to make it easier to keep track of systems in different time zones around the world.

It is now possible to evoke a TELNET command that a uses a initial program depending on the Condition name in Warning. Also, a new command has been developed for installation monitoring more than one system: If you are signing on with the same user and password on all of the remote systems, you only have to enter the user id and password once every day.  

The program that monitors the current disk percentage used for the System ASP has been changed. Before, when the disk percentage was close to the threshold limit, i.e. varying a little bit above and under the threshold limit, the status would also be switching between Warning and normal. This function has now been improved.

The maximum parameter value for the total jobs on system has been increased from 99.999 to 99.999.999 jobs.

Use the Check PTF Group Status (PCHKPTFGRP) command to check status for all PTF groups on system. The PTF will be checked by looking at the current status. You may specify a list of valid statuses. You may also specify a list of PTF groups to be ignored. Use the Display PTF Group Status (PDSPPTFGRP) command to display status for PTF groups.

Use the Check PTF status (PCHKPTFSTS) command to check status for all PTFs on system. The PTF's will be checked by looking at the current status and if any IPL actions are needed.

User options may now be used from the "Work with systems" and "Work with monitoring parameters" display.

A new function call Time tables may it easier to set up different monitoring time for individual objects and maintain the monitoring times.

Use the new Document System Monitoring parameters command (PDOCSYMPRM) to produce a list of the current checkpoints being monitored, including details for well known conditions such as:              

- A list of jobs / subsystems being monitored                

- Threshold values for Disk % monitoring  

Job Monitoring

==============

A new "widescreen" size display has been added. This gives you more information on a single screen.

Log messages will be sent for jobs in error from the Job Monitoring function.

A new command Change monitoring list entry (PCHGJBMLST) has been added. Use this function to hold or release an entry in a Job Monitoring list depending on if the same job exists in another list.

Use the "Compare monitoring list" function from the "Work with job monitoring lists" to check if jobs exists in both lists.

A new parameter CHKDUP has been added to the Merge monitoring list (PMRGMONLST) command.

Message monitoring

==================

Several new substitution variables have been added and may be used in the "Command to execute":

&ERRID &OBJLIB &OBJTYP &OBJ &PGMLIB &PGM &FILLIB &FIL &MBR &NBRRCD &DLTRCD &MSGVAR01

Note: Some of them are only supported for certain Message Ids.

Use the Display message queue (PDSPMSGQ) to display the QSYSOPR message queue:

Compared to the ordinary DSPMSG command, the PDSPMSGQ gives you:

- Direct access to work with the job that sent the message    

- Direct access to display the job log for the job        

- Work with history for a message Id    

Configuration monitor

======================

Status will be set to Warning if a a configuration objekt being monitored no longer exists. On the "Work with configuration status" screen this will be displayed as "*FAILED" as status and "*UNKNOWN" as description.

A new command has been added. Use Check Configuration Object (PCHKCFGOBJ) command to verify if a configuration object have a certain status. Optionally, a CL command may be specified to be executed if the object has the wrong status.

The Check TCP/IP function may be used to verify if another node in the network is reachable by using the Ping command. Some new parameters have been added:

- Log statistics: Specifies whether statistics should be logged to a database file.      

- Hold: Use this parameter to temporarily hold an IP address from being monitored.                

- Monitoring time table

Journaling

==========

The maximum size for a work file has been increased.

System operation

=================

A new enhanced version of the Work with Active jobs (PWRKACTJOB) has been added. This is using screensize 27x132 and therefore gives you a lot more information on a single screen. Also it has advanced function to search for certain jobs.

Reports

=======

A new command may be used to Convert disk information reports to HTML reports in the IFS.

Job history

===========

Use the new BWSTAT03 command each day to gather information for a subsystem job and compare this to expected uptimes for the subsystem.

Errors in the release?

======================

PPRTDSKINF              

How do i check what version of OPRS i have?

How do i check what version of OPRS i have?

Sometimes you will need to know what release of OPRS you are running. Specially if you are about to upgrade your OS or OPRS itself, you need to know what release you have. When you contact us about anything releated to OPRS, one of the first questions that we will ask you, is what version of OPRS you are running.

The answer is right in front of you, hit PDS and Enter, and then look at the top of the screen, it will say something like: OPRS Major menu - Release X.X. where X symbolize the actual release number, i.e. 9.3. If you dont use the standard delivered PDS command for accessing the OPRS system, use the one you created instead.