JobRescue™ Administrator’s Reference GuideChapter 1 Using JobRescue Nobix JobRescue Administrator’s Reference Guide 8 JobRescue can also verify that certain messages actually

JobRescue™ Administrator’s Reference Guide MPE/iXVersion 6.1f

JobRescue™ Administrator’s Reference Guide(MPE/iX)

Version 6.1fJune, 2005

The information contained in this document is subject to change without notice.

Nobix, Inc. makes no warranty of any kind with regard to this material, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Nobix, Inc. shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance or use of this material.

This document contains proprietary information that is protected by copyright. All rights are reserved. No part of this document may be photocopied, reproduced or translated in any form, or into any other language, without the prior written consent of Nobix, Inc.

© Copyright 1990, 1991, 1993, 1996-1999, 2000-2003 by Nobix, Inc., San Ramon, California, Phone 800.538.3818 or 925.659.3500, Fax 925.659.3599.

e3000 and MPE/iX are trademarks, registered trademarks, trade names, and/or products of Hewlett-Packard Company. JobQue and ElectroPage, are trademarks and/or products of Nobix, Inc. All other trademarks are the property of their respective holders.

Table of Contents

Table of Contents

PrefaceJobPak and Installation .....................................................................................................................5How this document is organized .......................................................................................................5Assumptions ......................................................................................................................................6Related documents ............................................................................................................................6Technical support ..............................................................................................................................6

Chapter 1 Using JobRescue ....................................................................................................................................7

Introduction ......................................................................................................................................7Error detection ..................................................................................................................................7Error handling ...................................................................................................................................8Reporting and archiving ....................................................................................................................8

Report viewing ...........................................................................................................................9

Chapter 2 Getting Started ....................................................................................................................................10

Startup ............................................................................................................................................10Running JobRescue .........................................................................................................................10

The CONFIGIX program ........................................................................................................10The STATUS program .............................................................................................................11Passwords and security ..............................................................................................................11

Stopping JobRescue .........................................................................................................................11

Chapter 3 The CONFIGIX Program ...................................................................................................................12

Introduction ....................................................................................................................................12Configuration menus ......................................................................................................................12Saving configurations ......................................................................................................................14Configuring global values ................................................................................................................15

Processing options ....................................................................................................................16Global error string text ..............................................................................................................18Post-processing options .............................................................................................................19Messaging configuration ...........................................................................................................20MPE :XEQ scripts ....................................................................................................................22Security level .............................................................................................................................22Miscellaneous system values ......................................................................................................23

Configuring job-specific values ........................................................................................................25Customizing error detection .....................................................................................................27$STDLIST save options ...........................................................................................................28Job-processing options ..............................................................................................................29Executing specific :XEQ files ....................................................................................................31E-mail distribution ...................................................................................................................32Modifying file access .................................................................................................................33Configuring folder organization ................................................................................................36Adding folders ..........................................................................................................................37Deleting folders ........................................................................................................................38Adding reports to folders ..........................................................................................................38Configuring retention management ..........................................................................................40

Nobix JobRescue Administrator’s Reference Guide 1

Table of Contents

Configuring reporting ...............................................................................................................41

Chapter 4 The STATUS Program ........................................................................................................................45

Line mode .......................................................................................................................................45Line mode conventions .............................................................................................................46

Command reference ........................................................................................................................48COPY .......................................................................................................................................50EXIT ........................................................................................................................................51FIND .......................................................................................................................................52HELP .......................................................................................................................................53LIST .........................................................................................................................................54LOG .........................................................................................................................................55MESSAGES .............................................................................................................................57REDO ......................................................................................................................................58RETRIEVE ..............................................................................................................................60SEARCH ..................................................................................................................................61SEARCHALL ...........................................................................................................................62SET ..........................................................................................................................................63SHOW .....................................................................................................................................64SHOWALL ..............................................................................................................................66SHOWFOLDER .....................................................................................................................67SHOWLOG ............................................................................................................................68SHOWDELETELOG ..............................................................................................................69STATS .....................................................................................................................................71TEXT .......................................................................................................................................72VERSION ................................................................................................................................73WIDTH ...................................................................................................................................74

Report mode ...................................................................................................................................75Viewer—folder tree ..................................................................................................................75Report viewing .........................................................................................................................79Report navigation .....................................................................................................................83

Chapter 5 The JPAKCOM Program ....................................................................................................................92

Running JPAKCOM .......................................................................................................................92JPAKCOM Commands ............................................................................................................93EXIT ........................................................................................................................................94MPE .........................................................................................................................................95PROCESS ................................................................................................................................96REINDEX ................................................................................................................................97RESUME .................................................................................................................................98STOP .......................................................................................................................................99SUSPEND .............................................................................................................................100

Chapter 6 The STDLOG Report .......................................................................................................................101

STDLOG configuration ................................................................................................................101Section I .................................................................................................................................102Section II ................................................................................................................................102Section III ...............................................................................................................................103


Table of Contents

Printing specific accounts ..............................................................................................................103Producing microfiche reports ..................................................................................................104Changing reporting defaults ....................................................................................................105

Chapter 7 Deferring $STDLISTs .......................................................................................................................107

Chapter 8 Advanced Features .............................................................................................................................108

Delay $STDLIST examination ......................................................................................................108Special :COMMENT lines ...........................................................................................................108

Controlling text examination ..................................................................................................109Contents of MPE :XEQ scripts ...............................................................................................109

Action control sheet ......................................................................................................................110Substitution values ..................................................................................................................111Additional alterations ..............................................................................................................111

Appendix A The AutoDial Program .....................................................................................................................114

Pager networks ..............................................................................................................................115Using AutoDial .............................................................................................................................115

System setup ...........................................................................................................................115PHONE file ..................................................................................................................................115

PHONE record format ...........................................................................................................116Enabling AutoDial ..................................................................................................................118AutoDial in test mode ............................................................................................................119

Error messages ...............................................................................................................................120

Appendix B The UNLOAD Program ...................................................................................................................121

Create an ASCII configuration file ..........................................................................................121Edit the ASCII configuration file ............................................................................................122Rules for editing the ASCII file ...............................................................................................122Backup the current configuration and load the edited ASCII file ............................................123Restore the backup configuration ............................................................................................123Print a configuration report ....................................................................................................124

Appendix C Standard Log Reports .......................................................................................................................125

STDCOPY listing ..................................................................................................................129

Appendix D Exception List Reports ......................................................................................................................130

Index .............................................................................................................................................134


PrefaceThis document provides operation, administration and configuration guidelines for the JobRescue software product from Nobix, Inc. If you’re new to JobRescue, you’ll learn the fundamental concepts and essentials necessary to use JobRescue effectively.

JobRescue is a best-of-class job management and error detection program for e3000 batch processing environment. By automatically detecting errors and exception messages, JobRescue eliminates the need for manual review of $STDLIST files, making batch processing operations more productive for Information Technology managers and staff.

Installed on thousands of systems worldwide, JobRescue is designed to improve the productivity of batch processing operation in single or networked e3000 environments.Easy to install and use, the program is preconfigured to trap job messages through a simple menu utility program. With its autodial capability, JobRescue can even notify users of critical messages via pager.

Once launched, JobRescue runs as an unattended batch job. As jobs log off, JobRescue automatically examines each $STDLIST. Multiple $STDLIST files may be processed simultaneously, saving time and money. JobRescue automatically compresses the $STDLIST files and saves them to disk, eliminating worries about lost or misplaced information while significantly reducing paper and printing costs.

$STDLIST files may be viewed online through the comprehensive viewing program that includes foldering and search capabilities. The lists can also be grouped by a user-definable time period and kept online for an indefinite period of time.

When used in conjunction with the Nobix JobQue product, JobRescue integrates error detection with scheduling to ensure that no job is considered finished before it is thoroughly examined.


Preface

JobPak and InstallationJobRescue is one of the three Nobix data center productivity tools bundled under the name JobPak. The JobPak tools consist of the following:

• JobQue

• JobRescue™

• ElectroPage™

Together these products offer information technology managers and staff the production class, system management capabilities needed to keep a single or networked e3000 systems running at peak efficiency. The JobPak tools are used as a standard by Hewlett-Packard IT centers and by HP customers worldwide to provide productive and efficient operations on the e3000.

Although the JobPak products can be purchased and used individually, they all run in the background under the JobPak batch job. The Installation of JobRescue, and/or any of the other JobPak products, is described in the JobPak Installation and Update Guide. Review this document before attempting to install or upgrade JobRescue or any of the other JobPak software tools.

JobRescue training classes are also available to provide training that will aid in administering JobRescue. Please check with Nobix regarding training schedules and cost.

How this document is organizedChapter 1, “Using JobRescue,” provides an overview of the JobRescue product and offers basic descriptions of its main features.

Chapter 2, “Getting Started,” describes how to start and stop the JobRescue program.

Chapter 3, “The CONFIGIX Program,” provides detailed information on how to modify the basic JobRescue configuration without stopping the program.

Chapter 4, “The STATUS Program,” provides detailed information on how to run and use the JobRescue STATUS program.

Chapter 5, “The JPAKCOM Program,” provides detailed information on how to run and use the JPAKCOM program.

Chapter 6, “The STDLOG Report,” describes what a STDLOG is and how STDLOGs are used within the JobRescue environment.

Chapter 7, “Deferring $STDLISTs,”describes JobRescue's capability to automatically defer $STDLISTs from printing.

Chapter 8, “Advanced Features,”describes JobRescue's advanced features.

Appendix A, “The AutoDial Program,” provides information on running and using the AutoDial program.

Appendix B, “The UNLOAD Program,” discusses the UNLOAD program which allows system administrators to make global changes to the configuration files contained within the CONFIGIX program.

Appendix C, “Standard Log Reports,”provides a sample STDLOG report.

Appendix D, “Exception List Reports,” provides a sample EXCPTLST report.


Preface

AssumptionsThis document assumes that the reader is familiar with e3000 computer systems and the MPE operating system. It is intended to be used by system administrators, managers and any other users of the JobRescue software utility.

Readers should also be familiar with the e3000 manuals published by the Hewlett-Packard Company.

Related documents• JobPak Installation and Update Guide

• JobPak Release Notes

• JobQue Administrator’s Reference Guide (MPE/iX)

• ElectroPage Administrator’s Reference Guide

• Nobix Web site www.nobix.com

Technical supportNobix provides 24x7 technical support (including weekends and holidays) for customers with current maintenance agreements.

The JobRescue software uses the latest operating system technology and requires an e3000 system running MPE/iX version 5.0 or later.

Nobix strives for efficient and reliable software; however, if you encounter any problems that this manual does not address, or find an error, contact Nobix technical support:

Nobix, Inc. 3180 Crow Canyon Place, Suite 255 San Ramon, CA 94583 925.659.3500 800.533.3818 925.659.3599 fax [email protected]

If you fax your question, include your name, phone number, and fax number on the cover sheet. Usually, we call you as soon as we receive your fax.

If you report a limitation or problem, we will either fix it or provide a workaround as soon as possible.

If you will allow us dial-up access to your machine, please have the dial-up number and passwords available. We do not sign on to every machine; however, sometimes it is easier to solve a problem when we can see it happen.

If you cannot find an answer in this manual, contact us!


Chapter 1 Using JobRescue

This chapter provides an overview of the Nobix JobRescue software for the HP e3000.

Introduction JobRescue is an HP e3000 software utility used in computer operations and system management.

JobRescue's error detection capabilities provide:

• Monitoring and documenting of all batch job completions

• Prompt determination of which jobs have errors

• Communication between departments using data processing

JobRescue eliminates wasteful printing of $STDLISTs by keeping them available online, outside the spooler, until no longer needed. This allows viewing and searching of job listings from any terminal or PC, local or remote, at any time.

Error detectionJobRescue checks each job listing for the default predefined error messages. Most, if not all, job errors will be caught by this error checking. The error message list can be modified to accommodate site specific requirements. Messages can apply to all jobs (global values), or be designated to apply to specific jobs (job specific values). In addition, global error messages can be deactivated for specific jobs. Complete flexibility is provided to handle any situation that might occur.

Note: Specified in the default configuration is a basic list of error messages. Messages can be added to or removed from this list.



JobRescue can also verify that certain messages actually do appear in the job listing. If a message that should appear is not found, JobRescue treats that job as though an error occurred. Of course, the message does not need to be an error message. It could be any text or phrase printed in the $STDLIST.

Error handlingWhen JobRescue finds an error or other job exception within a $STDLIST, the program notifies the operator and other users in two ways:

1 It sends messages to the system console indicating the job in question, and the information that an exception exists. These messages can then be sent to other online users. Optionally, messages can be deactivated at the console, or system-wide.

2 It prints a notification (the EXCPTLST file) to the line printer. This notification, referred to as an Exceptions List, includes three sections:

• Banner page—displaying Job ID.

• Text of the $STDLIST is printed with line numbers—the lines which caused the error are flagged above and below with a row of asterisks.

• Action Control Sheet for documenting the errors—it may be torn off, annotated by responsible personnel, and used to document the batch error. For details, refer to Chapter 8, “Advanced Features.”

When an Exceptions List is read, the job name and the cause of the problem can be readily identified. Appendix D, “Exception List Reports.” contains a sample EXCPTLST file.

JobRescue can be configured to perform specific action when an error is found. For instance, to aid in recovery or to stop subsequent batch processing from running, JobRescue can be configured to execute certain MPE commands globally or for specific jobs. For example, JobRescue can be instructed to run the AutoDial program and automatically send a message to a pager to notify someone of an error. For details, refer to Appendix A, “The AutoDial Program.”

JobRescue logs all its console messages to a message history file. This file can be accessed through the STATUS program, as described in Chapter 4, “The STATUS Program.” The message history file stores a preset number of messages and can be searched forward or backward. JobRescue can also be configured to perform a specific action if a job is examined and no errors are found. For instance, the program can be configured to execute certain MPE commands to continue processing.

Whether it detects an error or not, JobRescue saves a $STDLIST that has been examined as a permanent file. JobRescue can be configured to keep these files online for a certain amount of time or to purge specific $STDLISTs from the spool system immediately. For details, refer to the “Post-processing options” section in Chapter 3, “The CONFIGIX Program.”

Reporting and archivingJobRescue automatically documents all batch activity and creates a STDLOG report of all job listings. This report contains the text of all $STDLISTs (carriage controls removed). It also includes user-defined indexes and specific error messages.

Spoolfiles are aged in place and logically grouped for reporting purposes. No additional resources are used to move files around. Since reports and $STDLISTs have separate aging configurations and job statistics can be archived apart from the file text, this greatly



simplifies the file structure and processing. Reports and $STDLISTs can be reliably archived using standard MPE utilities, such as Store and Restore.

The file scheme uses non-recurring filenames, enabling simple retrieval, without danger of overwriting existing files. It is an uncomplicated process to restore files from a backup and make them available again in the STATUS program. For more information, refer to Report viewing in this chapter. All activity remains accounted for.

Report viewing

Batch history can be viewed online at any time using the STATUS program. The STATUS program enables viewing of current and previous days' $STDLISTs, as well as archived job statistics for each report or $STDLIST. Programmers and system managers can use the STATUS program to check on the completion of any job.

The STATUS program can display a one-line summary of each job examined, showing job number, logon ID, error status, number of lines and the time the job listing was examined, as shown in this example:

File# Job# JobName User.Account #Lines Ex Logoff-at Elap. Cpu

35 J8495 JOBPAK MGR.T61 1556 20050410 0918 1015 3073

13935 J5766 JOBPAK MGR.T61 270 20040729 1235 1219 3167

With only a few keystrokes, the STATUS program can be used to search for text in individual or groups of online $STDLISTs. Using editor-like commands (Line mode) or a menu-driven interface (Report mode), portions of text can be viewed and copies made.

Since security of job listings and other spoolfiles may be important, JobRescue allows security access to be set at the user, account and operator capability levels. By default, any user can view any job listing. For details, refer to Chapter 4, “The STATUS Program.”


Chapter 2 Getting Started

JobRescue is designed to allow quick restoration of the software from tape and immediate use. After installation, the JobPak job can be streamed, and JobRescue begins processing.

To install the software, refer to the JobPak Installation and Update Guide. This chapter describes how to start, run and stop the Nobix JobRescue software utility for the e3000.

StartupNobix supplies a job control file named JOBPAK.JPAK.NSD that starts JobRescue. If you have also licensed JobQue or ElectroPage, this file also starts these programs.

To start JobRescue (as well as JobPak), enter the MPE command:

:STREAM JOBPAK.JPAK.NSD

When JobRescue begins execution, it displays a logon banner on the system console. JobRescue proceeds to examine all READY $STDLISTs.

Running JobRescueJobRescue runs in the background under the JobPak batch job. If JobRescue is inadvertently terminated, just stream the job again. JobRescue should pick up where it left off without loss of data.

The CONFIGIX program

All of JobRescue’s configurable options are maintained by the CONFIGIX program. JobQue and ElectroPage also use this file.

To access the configuration program and menus, sign on as the NSD account manager:


Chapter 2 Getting Started

HELLO MGR.NSD

At the MPE prompt, type:

CONFIGIX.JPAK

CONFIGIX uses a forms-based menu interface to issue commands. Most of the commands are self-explanatory and easy to understand. For detailed descriptions of configuration commands, refer to Chapter 3, “The CONFIGIX Program.”

Note: Only one user at a time can make changes within the CONFIGIX program. Other users remain in a read-only status.

The STATUS program

All viewing and searching of saved spoolfiles, $STDLISTs and reports is done using the STATUS program.

To access the STATUS program, at the MPE prompt, type:

STATUS.JPAK.NSD

All $STDLIST activity and JobRescue information is available online via this program. For details, refer to Chapter 4, “The STATUS Program.”

Passwords and security

Most environments require the NSD account to be password protected or have some other adequate security protection. To provide this protection, modify the job control file JOBPAK.JPAK.NSD.

Caution: Do NOT alter the access parameters of the NSD account or the JPAK or PUB groups.

Stopping JobRescueTo stop JobRescue (as well as JobPak), enter the MPE command:

:JPAKCOM.JPAK.NSD

Note: Only users who have OP or SM (administrator) capabilities can use this command.

At the JPAK prompt, issue the STOP command by typing:

STOP

JobRescue will log off shortly afterward, as soon as all processing has been completed.

Note: If either ElectroPage or JobQue are licensed for use, they will also log off.

If JobRescue is inadvertently terminated, stream the job again. JobRescue picks up where it left off without loss of data.


Chapter 3 The CONFIGIX Program

This chapter describes how to use the menu-driven Nobix JobPak software configuration program.

IntroductionJobRescue provides the menu-driven program CONFIGIX to configure the software. The fully qualified program name is CONFIGIX.JPAK.NSD.

The Configuration program displays a user interface, allowing customization of JobRescue to meet specific site and application needs.

JobRescue's basic configuration can be modified by making changes with the CONFIGIX program even while JobRescue is running. The JobPak job does not need to be stopped first. JobRescue becomes aware of the change that is made and immediately loads it.

Note: Only one user at a time can make changes within the CONFIGIX program. Other users remain in a read-only status.

Configuration menusWhen the configuration program opens, the Main Configuration menu appears:



This is the Main Configuration menu used to access the submenus and commands. Function buttons appear at the bottom of the window, providing a shortcut method to execute commands. These buttons correspond to the F1—F8 function keys on your keyboard. (Some of these buttons remain undefined.)

The Main Configuration menu contains the following menu items:

• Configure GLOBAL Values—configuration information and default values applying to all jobs.

• Configure JOB Specific Values—configuration information specifically identifying jobs by logon ID.

• Configure FOLDER Organization—configuration setup for organization of report files for viewing purposes.

• Configure RETENTION Management—configuration time check, determining which files need to be deleted, based on length of save and when this program is to run.

• Configure STDLOG Report—configuration of the STDLOG report.

Use the UP and DOWN arrow keys to move through the menu. To choose a menu item, highlight the selection and press ENTER. (Menu selections with trailing dots indicate a path to another menu.) After a command is selected, a forms-based interface is displayed that prompts the user for any required input.

Certain CONFIGIX commands are job-specific, while others are global, as follows:



• Global commands apply to all $STDLISTs and spoolfiles.

• Job-specific commands apply to all $STDLISTs that match the qualifying pattern.

Procedures for configuring spoolfiles globally, or for specific jobs, are covered in “Configuring global values” and “Configuring job-specific values” in this chapter.

Saving configurationsAfter configuring spoolfiles, or making changes to the configuration, press F8-PREV SCREEN to save changes and exit the program. When the Main Configuration menu is displayed, press F8-EXIT PROGRAM and respond to the following screen prompt:

To save changes, tab to OKAY and press ENTER.

To exit without saving changes, tab to CANCEL and press ENTER. The program will return to the Main Configuration menu.

When a message such as “Config Modified” dynamically appears at the top of the menu or interface during a session, it is a reminder that modifications have been made to the configuration. See the following example:



Configuring global valuesTo configure global values, from the Main Configuration menu, select Configure GLOBAL Values. The Configure Global Values submenu appears:

The Configure Global Values menu offers the following options:

• Processing options—configures values that modify the logic used to determine where an error occurs.

• Global error string text—searches for specified character strings in every job examined.

• Post-processing options—determines how spoolfiles are to be treated after examination.



• Messaging configuration—determines the types of messages routed and their destinations.

• MPE :XEQ scripts—command files set up to process spoolfiles after a job is examined; executes up to six command files at a time.

• Security level—determines one of four levels of security for spoolfile access.

• Miscellaneous system values—system ID, location variables, and compression on/off.

Global commands apply to all $STDLISTs and spoolfiles. Detailed instructions for each item follow.

Processing options

To specify processing inputs for all jobs, from the Configure Global Values menu select Processing options. The Processing Options dialog box appears:

To modify the logic that determines how errors are processed in spoolfiles, enter values in each field as indicated below:

• Allow foreign spoolfiles—enter a Y here to have the current system recognize $STDLISTs from jobs on other systems or from a previous run (owned by jobs that have an apostrophe in job ID). An N instructs JobRescue to ignore such spooled files.

• Lowest output priority to process—enter a positive integer between 0 and 14 in this field to set the minimum output priority to which a $STDLIST can be queued and still be considered for examination by JobRescue.



• Highest output priority to process—enter a positive number between 0 and 14 in this field to set the maximum output priority to which a $STDLIST can be queued and still be considered for examination by JobRescue.

• Maximum number of $STDLIST lines to process—enter the maximum number of lines in a spoolfile that need to be processed. Some $STDLISTs can be quite large. Often the $STDLIST is larger than the configured maximum for spoolfiles on the system. If a $STDLIST has a greater number of lines than indicated here, it will be ignored.

• Follow Mpe IF/THEN/ELSE logic—enter a Y here to prevent JobRescue from detecting errors in un-executed portions of $STDLISTs.

When JobRescue detects a line containing the text “EXPRESSION FALSE: COMMANDS IGNORED...”, error checking is then turned off. When a line containing “RESUME EXECUTION OF COMMANDS” is found, error checking resumes.

• Check for :EOJ in every $STDLIST—enter a Y in this field to specify that any $STDLIST without an :EOJ is to be treated as an error. Unless all job control files contain the :EOJ, specify an N for this field. Otherwise, jobs that do not have it will be treated as though some error occurred.

Note: For more information, refer to “Job-processing options” in this chapter.

• Follow MPE :CONTINUE logic—to activate the :CONTINUE logic in JobRescue string searching, enter a Y in this field.

JobRescue stops $STDLIST examination for exception (or error) phrases at the line that contains the :CONTINUE. Examination for phrases picks up again when the second colon (:) following the :CONTINUE is encountered. Any error messages or other phrases between those two points are ignored.

This command allows suspension of error examination for short periods where anticipated errors may occur. This feature can be used to prevent any anticipated errors from being treated as exceptions.

• Empty spoolfiles (Ignore/Process/Delete)—enter a P to process any empty spoolfiles to be kept; enter an I for spoolfiles to be kept, but ignored; and enter a D to delete the spoolfile.

Processing a file might be a necessity if an application has generated a spoolfile that maybe important to log, even though the spoolfile is empty. This configuration option is intended for use with ElectroPage.

• Suppress banner on EXCPTLST—enter a Y to disable a banner page from automatically being attached to any Exceptions Lists; N is the default.

For an example of an Exceptions List report with a banner, refer to Appendix D, “Exception List Reports.”

• Suppress banner on STDCOPY—enter a Y to disable a banner page from automatically being attached to the STDCOPY listing; N is the default.

The STDCOPY listing is printed whenever JobRescue makes an automatic copy of a $STDLIST, as directed by a Copy :FILE command entry in the Job processing options configuration. For more information, refer to “Job-processing options” in this chapter.



Global error string text

To instruct JobRescue to search for certain character strings in all jobs, from the Configure Global Values menu, select Global error string text. The Global Error String Text dialog box appears:

There are seven predefined error messages that JobRescue checks for in the default configuration. Most, if not all, job errors will be found by this list. The error list can be customized to accommodate specific requirements. JobRescue does not have an internal limit on error commands.

To add a error text string to the list, press F1-Add Item and enter text into the displayed field at the bottom of the screen. Press ENTER to add the specified text to the list, as shown in the example above.

JobRescue handles the string of text as an exception when encountered in a $STDLIST, and searches every $STDLIST for every global error phrase as follows:

• If any non-displayable characters (ASCII value less than 32) are entered, JobRescue translates them into spaces.

• The entire text line to be searched for does not need to be defined; the phrase only needs to contain a portion of the text. For instance, the phrase “JOB FLUSHED” will actually capture the error string “REMAINDER OF JOB FLUSHED.” Character spacing and case are irrelevant, since all spaces are removed and the phrase is converted to upper-case.

To delete an error text string from the list, highlight the entry and press F3-DELETE ITEM. Tab to OKAY to complete.



To save your configuration changes, press F8-PREV SCREEN to return to the previous screen. Press F8-PREV SCREEN again to return to the Main Configuration menu. Press F8-EXIT PROGRAM and respond to the Save prompt.

For job specific error strings, refer to “Configuring job-specific values” in this chapter.

Post-processing options

To configure how JobRescue will handle $STDLISTs after examination, select Post-processing options from the Configure Global Values menu. The Post Processing Options dialog box appears:

Post-processing options can be used to keep files online a certain amount of time after they have been examined, to purge (or not purge) $STDLISTs after examination, and to set the printing priority to which non-$STDLIST spoolfiles will be adjusted after JobRescue examines them (requires ElectroPage).

Enter values in each field as described below:

• Default number of days to save $STDLISTs—enter a positive number here, between 1 and 9999. This number instructs JobRescue to keep $STDLISTs online for the indicated number of days.

JobRescue must be able to remove old $STDLISTs from permanent storage on disc. This maintenance action is important because without it, disc space would continue to fill up with $STDLISTs, beginning with the date JobRescue was installed. For configuration information on deleting saved spoolfiles, refer to “Configuring retention management” in this chapter.



• Purge $STDLISTs after exam—the default N prevents JobRescue from deleting $STDLISTs from the spool system after examination.

To conserve space, JobRescue examines a spoolfile, saves it as a permanent file, and deletes it from the spool system. The configuration can be set to purge globally by entering Y, and specifying certain files not to be purged. For details, refer to “$STDLIST save options” in this chapter.

• Default output priority for reports—this field applies to ElectroPage. Leave at value -1 for JobRescue.

• Compress all saved spoolfiles—the default N prevents JobRescue from performing LZ77 compression on all newly saved spoolfiles. Enter Y in this field to perform LZ77 compression.

When there are existing uncompressed spoolfiles,

– Y causes JobRescue to compress those previously uncompressed spoolfiles during idle periods.

– N does not cause JobRescue to uncompress existing compressed spoolfiles. They remain compressed. To uncompress these files, manually run the decompression program against each compressed file.

Messaging configuration

After JobRescue has examined a $STDLIST, it sends a message to the system console, and other users, indicating the name of the job examined. To control the message output to the console or to users, from the Configure Global Values menu, select Messaging configuration. The Messaging Configuration dialog box appears:



Enter a value in each of the fields, as described below:

• Disable examination messages—enter a Y in this field to prevent JobRescue from sending messages indicating the name of the job examined.

This setup does not prevent JobRescue from sending error messages to the console and other users.

• Disable console messages—enter a Y in this field to prevent all JobRescue messages from being output to the system console.

• Send messages to report creators—enter a Y in this field to have console messages sent to users.

Any user whose logon user ID and account matches that of an examined $STDLIST is notified of that examination.

Users can invoke the MPE command :SETMSG OFF, if they do not want to receive messages. The default is :SETMSG ON.

To allow additional users on the system to receive the same messages JobRescue sends to the console, add a list of these user names to the MPE file TELLUSER.JPAK. This file uses the same syntax as the MPE TELL command. The names should consist of the logon ID in the form of <jobname>,<user>.<account>, entered on one line. Add multiple names on one line, with the names separated by a semicolon, or add multiple lines.



MPE :XEQ scripts

To globally execute a set of MPE commands after a $STDLIST or other spoolfile has been examined, from the Configure Global Values menu, select MPE :XEQ scripts. The MPE :XEQ Scripts dialog box appears:

Up to six global commands can be configured with this menu.

Enter the filenames into the fields provided. Use only valid MPE filenames that are available for read access to the MGR.NSD user. For more information, refer to the “Contents of MPE :XEQ scripts” section in Chapter 8, “Advanced Features.”

The MPE commands are performed by JobRescue in the NSD account. JobRescue always executes the MPE commands after examining $STDLISTs and other spoolfiles. Files are executed in the order they appear, globally and then locally. See the “Executing specific :XEQ files” section in this chapter.

Note: To specify that no global MPE commands are to be performed for a specific $STDLIST or spoolfile, refer to “Job-processing options” in this chapter.

Security level

Typically, all $STDLISTs and spoolfiles examined by JobRescue are accessible by any user of the computer system. Security is controlled through the use of the STATUS program.

To assign security restrictions to saved $STDLISTs and spoolfiles, from the Configure Global Values menu, select Security level. The Security Level dialog box appears:



Enter a value at the Default security level for all spoolfiles prompt to set the level of standard security restriction. The available options are:

• 0—No security—any user can access any file.

• 1—Low security—users can access any files created in their own accounts.

• 2—High security—users can access only files they created. AM users can access any file in their account.

• 3—Check Access—users have no access unless specifically allowed. For details, refer to “Modifying file access” in this chapter.

Miscellaneous system values

To add the necessary system identifiers within one form, from the Configure Global Values menu, select Miscellaneous system values. The Miscellaneous System Values dialog box appears:



Enter a value in each of the fields, as described below:

• Company, Site, or Machine Name—enter a phrase containing up to 32 characters, including spaces, in the field provided.

The specified name will appear at the top of each page of the STDLOG report and on the Action Control Sheet. For multiple computer systems, give each system a different designation; this can assist in identifying which report belongs with each system. For more information, refer to Chapter 6, “The STDLOG Report” and Chapter 8, “Advanced Features.”

• Internet Mail ID—assigns a name to the JobPak software to use as the sender address for e-mail. Use a valid, standard internet mail format, such as:

[email protected]

This e-mail address also receives return mail when the address mail is sent to is incorrect or unavailable.

• SMTP Mail Server Hostname—enter the hostname of the network mail server.

• HPDeskManager ID—enter a valid user identifier, including a location and sub-location, to specify the public distribution list name. The user name should be followed by an at sign (@), and the location and sub-location separated by a forward slash. For example:



“JobRescue”@[DP/XX]

This field entry specifies JobRescue’s HPDeskManager identifier, enabling JobRescue to mail messages and deliver reports with the designated From address.

• Do at Startup—enter the name of the MPE :XEQ script file to be executed every time JobRescue starts up.

This entry allows JobRescue to execute a set of defined MPE commands when the program initializes. If JobRescue is stopped and restreamed, the commands are executed again.

• Number of Exam Processes—sets the maximum number of concurrent examination processes. The default is 5. The value must be in the range 1 to 100.

Configuring job-specific valuesThis section describes how to fine-tune the configuration to search for specific messages and to perform particular operations in certain jobs.

To configure job specific values, from the Main Configuration menu, select Configure JOB Specific Values. The Configure Job Specific Values submenu appears:

To add a file to be modified to the list, press F1–ADD ITEM and enter information into the fields, as follows:

• FileDes—the file designator ($STDLIST is the default).

• JobName—the name of the job.



• UserName—the name of the user who created the spoolfile.

• AcctName—the account in which the job logs on.

• Device—the device on which the $STDLIST was created.

This setup uses standard MPE formatting. If any portions of the logon ID are blank or missing, they default to the wildcard character “@”. For instance, if you specify only the User Name and Account Name, JobRescue assumes the Job Name is “@”.

Since job logon IDs can be wildcarded, you can specify processing for a large set of jobs using wildcards, and then define the exceptions without using wildcards. If a logon in a $STDLIST matches more than one wildcarded entry, JobRescue uses the first one on the list.

Alternately, select an existing file on the list to be modified, highlight it, and press ENTER.

The following Modification menu appears:

The name of the selected job appears at the top of the menu, as shown in the example. The Configuration Menu contains the following items:

• Error string text—configures text to be handled as an error

• Non-error string text—configures text for JobRescue to find, but not as an error

• Missing error string text—configures text that if missing causes an error condition

• $STDLIST save options—sets number of days specified file stays on the system after they have been examined



• Job processing options—configures values that modify the logic used to determine how a job is processed

• MPE:XEQ scripts—defines MPE execution exceptions for a particular job

• Email distribution: sends a message to a particular user after examining a particular file

• View access—configures security access for a particular file

• Pattern indexing—configures pattern index values

Procedures for each of these menu items are described below.

Customizing error detection

JobRescue searches for global error string text in all files. In addition, individual $STDLISTs can be searched for additional exceptions, specific to those $STDLISTs.

These error text strings are defined for individual $STDLISTs using one of the following modification options:

• Error string text—enter a string of characters for JobRescue to handle as an exception or error when encountered in a specific $STDLIST. There is no limit to the number of error commands that can be assigned to a $STDLIST.

• Non-error string text—enter a string of characters for JobRescue to find, but not to be found as an error. Use this to turn off certain broadly defined error strings with a narrowly defined non-error string, like when searching for the error string "not found", but only treat messages that do not include “myfile” as errors. It is necessary to define a non-error string, “myfile not found”.

• Missing error string text—specify a string of characters in this field that must appear in a $STDLIST. If the specified phrase is not found, that $STDLIST is treated as an exception and an Exceptions List is printed. For an example of this list, refer to Appendix C, “Standard Log Reports.”

To modify error string text, highlight one of the above options on the Modify Configuration menu, and press ENTER. The appropriate dialog box appears similar to the example below.



Press F1–Add Item and enter text in the corresponding field that appears at the bottom of the form. Press F8–PREV SCREEN to save changes and return to the Modify Configuration screen. Continue to press F8 until you can respond to the Save & Exit screen prompt.

Note: When searching for job-specific errors, JobRescue removes spaces and changes text to upper-case before the comparison.

$STDLIST save options

JobRescue globally saves spoolfiles after they have been examined according to the number of days specified in Post-processing options as described in this chapter. The number of versions, or generations, to be kept can also be specified. $STDLISTs are always kept online for at least one day.

To modify the length of time a particular $STDLIST is kept online, from the Modify Configuration menu, select $STDLIST Save options. The $STDLIST Save Options dialog box appears:



Enter values in the fields in the displayed form, as described below:

• Number of days to save this $STDLIST—enter a positive number (up to 9,999) which will keep this $STDLIST online for the indicated number of days.

Since the system will keep a $STDLIST for a minimum of one day, the default is to use the global value if this field contains a zero or is blank.

• Number of generations to save of this $STDLIST—enter a number to indicate how many generations (versions) of a job to be kept.

This field may be used in conjunction with the previous field. For instance, specify three generations of a job to be kept no longer than ten days. If the generation field contains a zero or is blank, save by number of generations is disabled.

Job-processing options

When you select Job processing options from the Modify Configuration menu, the Job Processing Options dialog box appears:



The items listed correspond to the options described in “Processing options” on page 16. They include:

• How to proceed—enter a number from 0 to 3, to specify:

0—process normally and always save the $STDLIST.

1—bypass; do not process; no other options apply.

2—if errors are not found, do not save.

3—delete the $STDLIST and do not process.

Note: If the following options do not have assigned values, the system refers to the Global settings specified for these same options.

• Delete spoolfile afer processing—entering a Y in this field causes the OUTPRI and DEVICE fields to have no effect (see the next two items below). The $STDLIST is deleted from the spool system.

• Set to this OUTPRI after processing—enter a value from 1 to 14. Entering a -1 in this field ensures that the original output priority is restored.

• Set to this device after processing—specify the device on which to print the spoolfile.

• Follow MPE :IF commands in $STDLISTs—enter a Y in this field if you want JobRescue to recognize IF logic in a $STDLIST. JobRescue will skip false conditions.



This means that when JobRescue detects the line of text: “EXPRESSION FALSE: COMMANDS IGNORED...” error checking is turned off. When a line containing “RESUME EXECUTION OF COMMANDS” is found, error checking resumes. The primary use of this command is to prevent JobRescue from detecting errors caused by the MPE :TELL command within job streams.

• Check for :EOJ in $STDLIST—enter a Y in this field to ensure JobRescue checks any $STDLIST for an :EOJ. If an :EOJ is not found, an Exceptions List is printed and the $STDLIST is treated as though an error occurred.

An :EOJ can be missing from a $STDLIST because the job control used to stream the job did not contain an :EOJ; because the job never completed; or, because the job was executing at the time the system crashed.

• Ignore errors after :CONTINUE—enter a Y in this field to instruct JobRescue to stop $STDLIST examination for exception (or error) phrases at the line that contains the :CONTINUE.

This command enables suspension of error examination in a job, for short periods where anticipated errors may occur. Examination for phrases picks up again when the second colon (:) following the :CONTINUE is encountered. JobRescue ignores any error messages or other phrases between those two points.

• Disable global error checking—enter a Y in this field to only look for local error messages.

• Disable global XEQ’s—enter a Y in this field to execute only job-specific MPE command files.

• Copy :FILE Command—enter the MPE :FILE command to direct where the copy of the $STDLIST should be sent. The job is then printed to this file command.

• EXCPTLST :FILE Command—enter the MPE :FILE command to direct where the copy of the $STDLIST should be sent, if found with some type of exception. The job is then printed to this file command. The default file command for EXCPTLST is in the JobPak.JPAK JCL file.

Do not include the colon (:) in the file equation. Do not use EXCPTLST for the file command.

Executing specific :XEQ files

To define MPE execution exceptions for a particular job, from the Modify Configuration menu, select MPE :XEQ Scripts. The MPE :XEQ Scripts dialog box appears:



Up to six job-specific commands can be configured with this menu. Enter the particular MPE script(s) to be added to the specified job in the fields provided. Then, tab to OKAY and press ENTER.

If both global and job-specific MPE commands are configured, JobRescue always executes the global execution files first. Refer to “MPE :XEQ scripts” in this chapter for more information.

E-mail distribution

JobRescue can be configured to send a message to a particular user after examining a particular file. The complete text of a file can also be sent. When a message is delivered, it is easy for the recipient to see that it originated with JobRescue.

From the Modify Configuration menu, select Email distribution. The following dialog box appears:



Press F1–Add Item and enter values in the three fields at the bottom of the screen, as follows:

• Note or List—enter an L or N to designate a complete listing or note, indicating that the complete text of a job should be sent, or just a message showing the job status.

• Error—enter an E to indicate sending as an error condition, or leave the field blank to indicate sending as a non-error condition.

• Address—enter the user’s Internet Email address or HPDeskManager address. Use the following format for the HPDeskManager address:

“username”@[location no./sublocation no.]

Use the following format for internet mail:

[email protected]

Modifying file access

File access is controlled at the global level by the security level configuration. If the global security level is set to check access, it is necessary to grant access to certain users. For details on global access setup, refer to “Security level” in this chapter. In addition, it is possible to extend additional access privileges to a user for a particular $STDLIST or spoolfile. Prior to modifying file access, verify whether a user already has the access privileges they require.



View access

From the Modify Configuration menu, select View Access. The name of the spoolfile to be modified appears at the top of the dialog box that appears.

Press F1–Add Item to assign view access to a user. Three fields appear at the bottom of the screen, as shown above. Enter the user’s logon ID as follows:

• Job/Sess—the job name or session.

• User—the name of the user who created the spoolfile.

• Account—the account in which the spoolfile was stored.

The following wildcards may be used to allow pattern matching: the at symbol (@), the pound sign (#), and the question mark (?).

Pattern indexing

Pattern indexing uses MPE pattern matching expressions to provide a means of delineating index values. In JobRescue, the pattern definition is treated as the index value. Pattern matching expressions provide an extremely powerful yet flexible language for pattern indexing. This provides maximum versatility in using virtually any character sequence or pattern to denote index entries, using MPE pattern matching characters and any literal characters, within a column or row range, as detailed below.

From the Modify Configuration menu, select Pattern indexing. A dialog box similar to the following appears:



Press F1–Add Item to enter a new pattern index. Nine entry fields appear at the bottom of the screen, corresponding to the six parameters described below (the pages, rows and columns entries each have a beginning and ending field). The numbers entered here must be relative to 1; a 0 indicates that the information in a field is not to be used.

• Pages—enter the beginning page number and the ending page number in the first and second fields, respectively.

• Rows—enter the beginning row number and the ending row number in the third and fourth fields, respectively.

• Cols—enter the beginning column number and the ending column number in the fifth and sixth fields, respectively.

• Length—enter the number pertaining to maximum length of the index value.

• Pattern—enter the pattern, using standard MPE pattern matching characters: the at sign (@) matches any single or multiple character sequence; the pound sign (#) matches any single digit; the question mark (?) matches any single character. All other characters correspond to themselves.

• Description—enter a description of the index value; for example, account number.

The Pattern and Description fields can contain a maximum of 30 characters. When an entry is completed in the other fields, a dash is automatically added as a separator between one number and another, as in 0–999.



To reconfigure existing index values already assigned to a saved spoolfile, refer to the REINDEX command in Chapter 5, “The JPAKCOM Program.”

The STATUS program can be used to view available $STDLISTs and reports with indexes, and to display index values. Refer to Chapter 4, “The STATUS Program.”

Configuring folder organization

JobRescue can be configured to create an on-line folder tree to store $STDLISTs inside folders. The STATUS program can then be used to view the $STDLISTs (described in Chapter 4, “The STATUS Program.”).

To access this feature, from the Main Configuration menu, select Configure FOLDER Organization. The Configure Folder Organization dialog box appears.

The JOBPAK FOLDER acts as an anchor for the folder organizational system. Like a file cabinet, it holds all the other folders in the system.

The folder system is hierarchical with successive levels of folders that contain other folders. The first level of folders are referred to as top-level folders. The next level is indented by a leading period. Each subsequent level is indented by an additional leading period. For instance, one leading period is equivalent to the first level down from the top level; two leading periods is equal to the second level, and so on.

There is no limit to the number of hierarchical levels that can be created. Ten levels are visible on the screen at one time. Folders within each level are sorted alphabetically and numerically.

In the example above:



• There are three visible top-level folders: ALL-REPORTS, BATCHNET_REPORTS, and BKP_REPORTS.

• In the BATCHNET_REPORTS folder, there is one first-level folder: batchnet_subfolder.

Folders might or might not contain reports. Viewing access must be designated for each folder, as described in Configuring report access in this chapter.

Note: JobRescue allows multiple folder paths to be created to locate a folder (and its contents).

Adding folders

To add folders to a folder tree:

1 Position the cursor on the folder within which the new folder is to be added (it is not necessary to position the cursor on the JobPak folder when adding top-level folders). Use the UP and DOWN arrow keys to scroll through the folder list.

2 Press F1–ADD FOLDER. Several fields appear at the bottom of the screen. Enter a Y in the Toplvl field to create a top-level folder. Enter an N to add lower-level folders. Lower-level folders are the default if this field is left empty.

3 Tab to the Name field. Enter a name for the new folder. A name can be up to 32 characters long. Your entry will default to upper-case letters. Tab to OKAY and press ENTER. If you change your mind, select CANCEL.

4 To save the configuration, press F8 until the Save/Exit screen prompt appears. Tab to



OKAY and press ENTER before exiting.

Deleting folders

To delete a folder:

1 Position the cursor to highlight the unwanted folder, and press F3-Delete Entry. Respond to the screen prompt to complete or cancel the action.

2 Tab to OKAY and press ENTER. The folder and the report specifications inside of the folder are deleted.

Adding reports to folders

To add a report to a folder:

1 Position the cursor to highlight the folder in which to enter a report and press F2-Add Report. Five fields appear at the bottom of the screen.

2 Enter values into the five fields as described below:

• File designator—spoolfile name

• Job name—job session or name

• User name—the name of the user who created the file

• Account name—the account in which the spoolfile was created

• Device name—device from which the spoolfile originates



Each field is limited to eight characters.

Reports can be viewed using the STATUS program as described in the “Report mode” section of Chapter 4, “The STATUS Program.”

In order to have $STDLISTs appear in folders, $STDLIST must be used explicitly in the file designator field. Wild cards apply only to reports in this field.

Configuring report access

By default, any user can view any folder. To restrict user access to a specific folder, highlight the folder and press F4–SPECIFY ACCESS. A dialog box similar to the following appears:

The selected folder is listed at the top of the form. Press F1-Add Item to assign access to a particular user. Three fields appear at the bottom of the screen. Enter the user's logon ID as follows:

• Job/Sess—the job name or session.

• User—the name of the user who created the spoolfile.

• Account—the account in which the spoolfile was created.

Users not included in this list will be restricted from viewing the folder. Wildcarding can be used with three types of pattern matching: the at sign (@), the pound sign (#), and the question mark (?).



If a view access list is not specified for a folder, view access is determined by the global security level configuration and any access configuration at the file or report level.

Note: Access configuration assigned to an upper-level folder applies also to any folders within it.

Configuring retention management

The Retention Management cycle consists of the production of the STDLOG report, the logtime periods, and the deletion of files that have aged beyond their lifespan.

The period of time in which a set of $STDLISTs is saved is referred to as a Log. Each time the Retention Management cycle runs, a new set of $STDLISTs becomes available as the current set, or Log 0. The 0 applies to $STDLISTs that have not yet been through a Retention Management cycle.

Retention Management acts on the $STDLISTs that can be displayed when running the STATUS program, and entering the SHOW command.

The Configure RETENTION Management setup command within the CONFIGIX program can be used to schedule predetermined days and times to initiate the retention management cycle, using the following configuration screen:

Enter the day and time a Retention Management cycle is to be scheduled, as follows:

1 Mark an X in one or more of the day-of-the-week fields.

2 Enter the hours and minutes in 24-hour time. The cycle will take place on the day(s) of the week marked with an X.



The merging of $STDLISTs into the STDLOG report automatically takes place during the scheduled retention management cycle, as follows:

• The MPE command file MERGE.PUB is executed.

• The Retention Management program loads the configuration information that is maintained with the configuration program.

• All files are scanned and the files that have aged beyond what is allowed by the specified configuration are deleted.

• A new log is created, and the log information is updated to show Log 1 as being the period of time from the most previous Log 1 to the current date and time. The previous Log 1 and other Logs are then incremented by 1, beyond their current Log numbers.

Use the SHOWLOG command in the STATUS program’s Line mode to see the updated times. Deleted files are logged to the delete log file and this log may be displayed using the SHOWDELETELOG command in STATUS.

Configuring reporting

A STDLOG report contains information about the most recently examined $STDLISTs. A STDLOG contains three sections:

• Section I—an index of all jobs examined

• Section II—user-defined indexes

• Section III—the text portion of the $STDLISTs

The index references in Sections I and II tell where to find the text in Section III. Indexes help locate text in Section III quickly, which is increasingly important as batch activity increases.

Appendix C, “Standard Log Reports,” contains a sample STDLOG report. For detailed information about the field and indicators in a STDLOG report, refer to Chapter 6, “The STDLOG Report.”

To configure a STDLOG report, from the Main Configuration menu, select Configure STDLOG Report. The Configure STDLOG Report dialog box appears:



The following commands are available:

• Sort Options—the format of the STDLOG report is controlled by modifying sort sequences or options. Reports contain job indexes in Section I; these indexes are the key to the body of the report, which contains the text of the $STDLISTs. For more information, refer to “Sort options” in this chapter.

• Index String Definitions—enables the creation of indexes in the STDLOG report. Section II lists user-defined indexes. For more information, refer to “Index string definitions” in this chapter.

Sort options

To modify sort sequences or options, from the Configure STDLOG Report menu, select Sort Options. The Sort Options dialog box appears:



Enter values in the fields provided as described below:

• Index page sorted by Account—enter a Y in this field to instruct JobRescue to sort the job index in account sequence, followed by job name sequence.

This becomes the default, if a particular sequence is not specified.

• Index page sorted by Job Number—enter a Y in this field to instruct JobRescue to sort the job index in job number sequence.

If the program encounters a non-consecutive job number, it flags it with an asterisk (*) to highlight this condition.

• Index page sorted by Job Name—enter a Y in this field to sort the job index in job name sequence, followed by account sequence.

This entry causes a job index to be printed in the STDLOG in job name sequence.

Note: Enter an N in any field that is not to be used to sort the job index.

Index string definitions

To define index strings, from the Configure STDLOG Report menu, select Index String Definitions. The Index String Definitions dialog box appears:



The text strings entered in this configuration will be used to create index pages in the STDLOG report. Any text found in a $STDLIST can be indexed with the appropriate phrase and will be listed in Section II of the STDLOG report.

Press F1–ADD ITEM and enter a string of characters to index. The phrase can contain up to 20 characters, including spaces. If more than 20 characters are entered, JobRescue ignores them. There is no limit to the number of phrases you can add.

If JobRescue does not find text in the $STDLIST that matches the index phrase, it will not print that index page.

For a detailed explanation of each section of the STDLOG report, refer to Chapter 6, “The STDLOG Report.”


Chapter 4 The STATUS Program

The STATUS program allows users to interactively view and search saved spoolfiles. After JobRescue has examined and saved a spoolfile, the $STDLIST will be available online via the STATUS program. The saved $STDLISTs can be accessed using command line entry in Line mode, or a user interface in Report mode.

The STATUS program provides:

• Index selection and search.

• User-defined function keys.

• Forward/backward search.

• Inclusion of $STDLISTs into folders.

• Suppression of PCL data, for easier viewing.

• Support of vertical single line and page scrolling.

• Support of horizontal single line and multiple-column scrolling.

• Ability to save user preferences.

Line modeTo operate the STATUS program in Line mode, at the MPE prompt type:

status.jpak.nsd

In Line mode, $STDLISTs are viewed using line-by-line command entry combined with specific parameters, as detailed below.



Line mode conventions

The parameters described below are used in certain Line mode commands described in this chapter.

Note: Quoted strings in STATUS must be surrounded by punctuation characters (in ASCII: any printed character except digits, letters or a space).

Parameters Descriptions

[FCTL|NOFCTL] Either a FCTL keyword (File Control) or NOFCTL keyword (No File Control).

FCTL is the default. When this keyword is used, JobRescue will copy any FCONTROL and FDEVICECONTROL records as they appear in the texted file.

The NOFCTL keyword tells JobRescue not to copy FCONTROL or FDEVICECONTROL records in the texted spoolfile.

JobRescue never copies FCONTROL and FDEVICECONTROL records to a disc file, no matter how this parameter is set.

[CCTL|NOCCTL Either a CCTL keyword (Carriage Control) or NOCCTL keyword (No Carriage Control).

CCTL is the default. This keyword tells JobRescue that the resulting file should contain the same carriage control as the texted file.

The NOCCTL keyword tells JobRescue to delete carriage control characters when it performs the copy operation; these characters should not be part of the resulting file.

Note: Do not specify NOCCTL unless NOFCTL has also been entered.

[ALL] Tells JobRescue to show $STDLISTs that match the OKAY and EXCEPTIONS keywords (shown below). This is equivalent to:

SHOW [USER.]ACCOUNT ; OK,EX

[BACKWARD] An optional keyword that informs JobRescue to print the display on a last-in, first-out basis (LIFO). In other words, the most recent JobRescue messages are shown first.

Do not use a <phrase> parameter with this keyword.

[EXCEPTIONS] Tells JobRescue to show $STDLISTs found to have exceptions.

[MISSING] A phrase of specified text string that should be present in a $STDLIST and is not found.

[OFFLINE] Tells JobRescue to send the display to a file named STATUS, default device LP. The heading will include the date and time of the display.

[OKAY] Tells JobRescue to show $STDLISTs that were found to have no exceptions and were not copied.



[UNN] Suppresses line numbering for LIST commands using a <range> parameter.

<command> This is any valid STATUS command. Do not abbreviate these.

<file–number> This is the file number of the $STDLIST or IBM job listing to be accessed. Use the SHOW command to verify this number.

<job–name> This is a job name qualifier. It includes three parts, in the format:

<jobname>,<user>.<account>.

<log–num> This number informs JobRescue of the $STDLISTs to be accessed, beginning with currently available ones, and regressing in time to previous sets. Each time $STDLISTs are placed on the STDLOG report, a new set of $STDLISTs become available as the current set. For more information, refer to the “Configuring retention management” section in Chapter 3, “The CONFIGIX Program.”

The number 0 applies to $STDLISTs that have not been placed into a STDLOG report; 1 is the most recent log; 2 is the set just before 1; 3 is the set before 2, and so on.

<outfile> An output filename or referenced file equation.

By default, this is device LP, record length 132 characters with carriage control. If this file is to be a disc file, specify “DEV=DISC” on a referenced :FILE command.

In the following keywords, only one of any arguments that are separated by the pipe character (I) can be specified at one time.

<phrase> A character expression delimited by quotation marks (“) slashes (/), backslashes (\), or pipes (|). This parameter is optional.

<range> A range of lines in the currently texted file.

A range may be composed of either one or two of the following indicators:

Indicator Meaning

A number A line in the file

An asterisk The current line

L or LAST The last line

F or FIRST The first line

ALL Every line

Two indicators can be used to specify the beginning and ending of a range. They must be separated by the slash (/). A plus (+) or minus (-) displacement value can also be entered.



The job name uses standard MPE formatting, as in UPDATE,MGR.FINANCE. If any portions of the logon-ID are missing, they default to the wildcard character (@).

Not all parts of the logon ID are required. If only one part is used, it becomes the account name portion; JobRescue assumes that the session and user names are “@”. If the user name and account are specified, JobRescue assumes that the job name is “@”. If job-name is omitted, @,@.@ is used.

Command referenceThe STATUS program has two operation modes: Line mode and Report mode. The Line mode commands are:

<string> A character expression delimited by quotation marks (“), slashes (/), backslashes (\), or pipes (|).

Commands Description

COPY Copies a $STDLIST or report to another file.

EXIT Exits from STATUS.

FIND Searches for strings in $STDLISTs and reports

HELP Obtains help information on the terminal.

LIST * Lists lines of text to the terminal.

LOG Accesses a set of saved $STDLISTs.

MESSAGES * Views message history.

REDO Re-enters the last command with optional changes.

RETRIEVE Commands JobRescue to restore an archived $STDLIST.

SEARCH Searches a group of $STDLISTs for text strings.

SEARCHALL Searches $STDLISTs in all available log groups for text strings.

SET Switches various display options on and off.

SHOW * Displays information about examined jobs.

SHOWALL Searches for a job throughout all LOGs.

SHOWFOLDER Displays the folder structure.

SHOWLOG Displays the date and time of each LOG.

SHOWDELETELOG Displays record of $STDLISTs deleted from JobRescue.

STATS Prints statistics about jobs.

TEXT * Opens a $STDLIST or report.



The syntax for each of these commands is described in the remainder of this section. Also refer to Report mode in this chapter, to use STATUS within the user interface environment.

VERSION Prints the version number of STATUS.

WIDTH Adjusts the display width of printed text.

Note: It is recommended that you initially learn the commands indicated by an asterisk (*).

Commands Description



COPY

Function

This command copies lines from a saved spoolfile to a new file.

Syntax

Copy <range> <outfile> [FCTL|NOFCTL [CCTL|NOCCTL]]

Operation

This command tells JobRescue to copy lines within <range> from the currently-texted file to an output file.

Use the TEXT command to open a file first, before using this command. The TEXT file might be a $STDLIST, an IBM job listing or a report file.

Use the LIST command to verify that the selected range of lines to be copied is correct.

Example

>> :FILE LP;DEV=LP>> T 23>> COPY ALL *LP

These command lines will make an exact copy of the $STDLIST on the printer. Be aware that within the STATUS Line mode, an MPE command must be prefaced with a colon. Commas are optional.

>>>> :FILE MYFILE;DEV=DISC>> COPY ALL *MYFILE NOFCTL NOCCTL

These command lines will make a disc file copy named MYFILE of this $STDLIST.

See also

TEXT



EXIT

Function

Closes the STATUS program.

Syntax

EXIT

Operation

When this command is typed at the command prompt (>>), the STATUS program is terminated and you are returned to the MPE environment.

If you type EXIT from the >n> prompt, you are exited from the STATUS program.

Example

>> EXITEND OF PROGRAM.MPE:

See also

HELP, LOG



FIND

Function

Searches the current texted file for a string of characters.

Syntax

FIND <string>

Operation

This command tells STATUS to search the currently open file for occurrences of <string> and display those lines.

Before the string comparison is made, STATUS shifts both <string> and the file text to upper-case and converts any non-displayable characters to spaces.


Example

>>FIND “RUN MYPROG”23 :RUN MYPROG.PUB.ACCT;MAXDATA=300000>>F |INFO=“871015”|96 :RUN AP001G.OBJECT;INFO=“871015”;PARM=1234127 :RUN AP032G.OBJECT;INFO=“871015”

See also

SEARCH, TEXT



HELP

Function

Provides on-line information about the STATUS program.

Syntax

HELP [ <command > [ <item> ] ]

Operation

The HELP command gives you on-line Help in the use of the STATUS program.

The <item> entry in this case can be one of the standard MPE terms: PARMS, OPERATION, EXAMPLE or ALL.

There are two ways to invoke HELP:

1 Type the HELP command with no parameters to stay within the Help subsystem. Type EXIT to return to the STATUS prompt (>>).

2 Type the HELP command followed by <command> and optionally <item>. The STATUS program will display only the requested information. You are then returned to the STATUS prompt automatically.

Example

>>HELP>>HELP SHOWALL

See also

EXIT



LIST

Function

Displays lines in the current texted file on the terminal.

Syntax

LIST <range > [UNN]

OR

LIST [EXCEPTIONS|ERROR]

Operation

Displays lines within <range> in a currently open file on the terminal (via the TEXT command). If a range is not specified, JobRescue only lists the last line displayed. The [UNN] keyword can be used to suppress line numbering.

If the second format is used, JobRescue only displays the lines that are found to be an exception. This format applies only to $STDLISTs.

Specifying EXCEPTIONS tells JobRescue that to view only lines within the text that JobRescue considers to have caused the exception or error, or lines with text searched for that could not be found (missing).

The ERROR keyword can also be used with this command.

Example

>>LIST 1/LAST–5>>L ERROR

See also

SET, TEXT, WIDTH



LOG

Function

Allows access to $STDLISTs, relevant to a period of time they are saved online.

Syntax

LOG <log–num>

Operation

$STDLISTs are always kept for a minimum of one day, or until the next Retention Management cycle (Refer to Chapter 3, “The CONFIGIX Program.”) Use the LOG command to move from one day’s set of $STDLISTs to another.

$STDLISTs are saved in JobRescue for as long as their configuration dictates. The number of days $STDLISTs are kept is entered at the Post Processing Options dialog box. (Refer to Chapter 3, “The CONFIGIX Program.”)

The LOG command indicates the period of time when a set of $STDLISTs is saved. This period of time, referred to as a “log”, is the interval between two executions of the Retention Management cycle.

The log periods or intervals are recorded in a JobRescue control file. This file contains the beginning and ending date and time for each log.

Enter LOG 0 to display the current $STDLISTs. There is no limit to the number of logs allowed.

Note: If other $STDLISTs than those available at LOG 0 are examined, the command prompt changes to >n>, where n is <log-num> as entered.

To list the $STDLISTs within a current log, enter SHOW @.

The SHOWLOG command verifies the dates and times of the logs on the system.

Example

Log is 0, from 2005/07/29 10:20:27 –> present.>>log 3Log is 3, from 2005/07/23 00:00:23 –> 2005/07/24 00:00:28.>3>showlog

There are 28 logs available.

Log#: From Date/Time To Date/Time0 WED, 2005/07/29 10:20:27 –> present1 TUE, 2005/07/28 00:00:16 –> WED, 2005/07/29 10:20:272 FRI, 2005/07/24 00:00:28 –> TUE, 2005/07/28 00:00:163 *THU, 2005/07/23 00:00:23 –> FRI, 2005/07/24 00:00:284 WED, 2005/07/22 10:20:06 –> THU, 2005/07/23 00:00:235 TUE, 2005/07/21 00:00:23 –> WED, 2005/07/22 10:20:066 FRI, 2005/07/17 00:00:26 –> TUE, 2005/07/21 00:00:237 THU, 2005/07/16 00:00:25 –> FRI, 2005/07/17 00:00:268 WED, 2005/07/15 10:20:06 –> THU, 2005/07/16 00:00:259 TUE, 2005/07/14 00:00:25 –> WED, 2005/07/15 10:20:06



10 FRI, 2005/07/10 00:00:24 –> TUE, 2005/07/14 00:00:2511 THU, 2005/07/09 00:00:24 –> FRI, 2005/07/10 00:00:2412 WED, 2005/07/08 10:20:06 –> THU, 2005/07/09 00:00:24

See also

EXIT, SEARCH, SHOW, SHOWLOG

Configuration file commands: Configure RETENTION Management, Post-processing options.



MESSAGES

Function

Displays the most recent JobPak console messages.

Syntax

MESSAGES [ <phrase> |BACKWARD ]

Operation

This command displays the most recent JobPak messages that have been issued to the system console on your terminal.

All JobPak messages, including those issued by JobQue, are displayed.

Each message line includes the relative message number and the time at which the message was issued.

When the <phrase> parameter is used, JobRescue will only print messages containing a matching character string. If the MESSAGES command is used without parameters, messages will be displayed in a FIFO sequence (first in, first out). If the keyword BACKWARD is used, messages are displayed in a LIFO (last in, first out) sequence.

Example

>>messages

SUN—2005/07/19

7481 10:46:06 Begin #2071, TEST5–VERSION61–SABER, step 20.7482 10:46:12 #J4019, TST61J02,MGR.NERDLERN has been examined.7483 10:47:05 Begin #2071, TEST5–VERSION61–SABER, step 30.7484 10:47:12 #O30451, #J4020, TESTOUT:TST61J03,MGR.NERDLERN has been examined.7485 10:47:20 #J4020, TST61J03,MGR.NERDLERN has been examined.7486 10:48:05 Begin #2071, TEST5–VERSION61–SABER, step 40.7487 10:49:40 #J4021, TST61J04,MGR.NERDLERN has been examined.7488 10:50:04 Begin #2071, TEST5–VERSION61–SABER, step 50.7489 10:50:19 #J4022, TST61J05,MGR.NERDLERN has been examined.7490 10:51:04 Begin #2071, TEST5–VERSION61–SABER, step 60.7491 10:51:31 #J4023, TST61J06,MGR.NERDLERN has been examined.7492 10:52:06 Begin #2071, TEST5–VERSION61–SABER, step 80.7493 10:52:12 #O30456, #J4024, TESTOUT:TST61J08,MGR.NERDLERN has been examined.7494 10:52:19 #J4024, TST61J08,MGR.NERDLERN has been examined.7495 10:53:05 Begin #2071, TEST5–VERSION61–SABER, step 90.7496 10:53:10 #O30458, #J4025, TESTOUT:TST61J09,MANAGER.SYS has been examined.7497 10:53:33 #J4025, TST61J09,MANAGER.SYS has been examined.7498 10:54:02 Schedule 2071, TEST5–VERSION61–SABER has ended normal.

See also

EXIT, SEARCH, SHOWLOGConfigure Global Values command: Messaging configuration.



REDO

Re-enters the last command with or without changes.

Syntax

REDO

Operation

When the REDO command is entered, the STATUS program displays the last command entered and allows changes to be made to it. When editing is complete, press ENTER to display the edited command. Press ENTER again to re-submit it to STATUS.

Editor commands

REDO uses standard editor syntax to make changes. The R command replaces characters, the I command inserts new characters and the D command deletes characters, as described below.

R—use the space bar to move the cursor to the location of characters to be replaced.

Press R and immediately type in the replacement characters. Press ENTER to display the edited command.

Example

>> SHOSUNKNOWN COMMAND>> REDOSHOS

RW <Return>

I—use the space bar to move the cursor to the position where characters are to be inserted. Press I and immediately type in the new characters. Press ENTER to display the edited command.

Example

>> SHWUNKNOWN COMMAND>> REDOSHW

IO <Return>SHOW

D—use the space bar to move the cursor to the position where characters are to be deleted. Press D once under every character to be deleted. Press ENTER to display the edited command.

Example

>> SHOUWUNKNOWN COMMAND>> REDOSHOUW



D <Return>SHOWMultiple changes—When ENTER is pressed once, STATUS displays the edited version of the command. After ENTER is pressed once to display the edited command, additional changes can be made to the text. Press ENTER again to send the new command to STATUS.

Example

>> SHUWUNKNOWN COMMAND>> REDOSHUW

D <Return>SHW

IO <Return>SHOW <Return>



RETRIEVE

This command causes JobRescue to capture the archived $STDLIST file(s).

Syntax

RETRIEVE <filename> [OLDDATE|NEWDATE]

Operation

The RETRIEVE command is used to restore a file that was previously deleted from JobRescue.

Files retained by JobRescue, via the Retention Management cycle, should be backed up as part of normal system backup procedures. Once a file has been deleted by the Retention Management cycle, the only way to bring that file back is to restore it from the system backup media.

To determine which file to restore from the backup media, use the SHOWDELETLOG command, which displays the logon IDs of $STDLISTs, as well as the filenames they were saved under, while retained in JobRescue.

• The OLDDATE keyword causes the original save dates to be restored; this is the default. The original date and time the file was saved is shown when the SHOW command is used.

• The NEWDATE keyword causes the current date and time to be attached to the restored file.

When an uncompressed file is restored based on information obtained from SHOWDELETLOG, both the base spoolfile and the associated header file must restored as well. The header file is named the same as the base spoolfile, but contains the extension .hdr at the end of the base filename.

Compressed files encapsulate the header information inside the compressed file, and therefore do not use a header file. Compressed files end with the extension .cmp.

Note: You must be signed on as MGR.NSD to perform this operation. The file must have been restored into the NSD account before using the RETRIEVE command.

Example

Log is 0, from WED, JUL 26, 2005, 4:44 PM –> present.>>RETRIEVE /NSD/files1/A1234.9876543213.cmp OLDDATENote: No pre–defined index information will be restored.searching Jobdata.Pub for /files1/A.1234.987654321.cmpentry added>>

See also

SHOWDELETELOG, TEXT

Configuration file command: Configure RETENTION Management.



SEARCH

Searches all $STDLISTs—in the log group you are currently in—for a text string.

Syntax

SEARCH [ <job–name> ] <string> ]

Operation

The SEARCH command tells STATUS to search for occurrences of a specified text string in any examined $STDLISTs, within the currently open log group, that match <job-name>. If a job name is not entered, JobRescue searches every $STDLIST that you have access to.

The currently open set is the current examined $STDLISTs or the set of $STDLISTs that pertain to a particular Log (see the LOG command).

The search begins with the most recently examined $STDLIST and continues to the oldest examined $STDLIST, displaying in descending date/time sequence. JobRescue shifts all text to upper-case and converts all non-displayable characters to spaces.


Example

>>SEARCH "CPU SEC"Will search 2 file(s) for "CPU SEC".Log #0 file #35, files1/A.14613.897495933, #J8495, $STDLIST:JOBPAK,MGR.T61

1554 CPU sec. = 3073. elapsed min. = 1015. MON, APR 10, 2000, 9:18 AM.Log #0 file #13935, files1/A.32798.901740108, #J5766, $STDLIST:JOBPAK,MGR.T61

268 CPU sec. = 3167. elapsed min. = 1235. WED, JUL 29, 2005, 12:19 PM.

See also

FIND, LOG



SEARCHALL

Searches all $STDLISTs, in all log groups that are available, for a text string.

Syntax

SEARCHALL [ [ <job–name > ] <string> ]

Operation

The SEARCHALL command tells STATUS to search for occurrences of a specified text string in any examined $STDLISTs, within all available log groups, that match <job-name>. If a job name is not entered, JobRescue searches every $STDLIST that you have access to.

The search begins with the most recently examined $STDLIST and continues to the oldest examined $STDLIST, displaying in descending date/time sequence. JobRescue shifts all text to upper-case and converts all non-displayable characters to spaces.

Example

>>SEARCHALL "CPU SEC"Will search 5 file(s) for "CPU SEC".Log #0 file #35, files1/A.14613.897495933, #J8495, $STDLIST:JOBPAK,MGR.T61

1554 CPU sec. = 3073. elapsed min. = 1015. MON, APR 10, 2000, 9:18 AM.Log #0 file #13935, files1/A.32798.901740108, #J5766, $STDLIST:JOBPAK,MGR.T61

268 CPU sec. = 3167. elapsed min. = 1235. WED, JUL 29, 2005, 12:19 PM.Log #1 file #13934, files1/A.32795.901652860, #J5764, $STDLIST:JOBPAK,MGR.T61

594 CPU sec. = 12911. elapsed min. = 5565. TUE, JUL 28, 2005, 12:06 PM.Log #25 file #1899, files1/A.14776.898019336, #J8621, $STDLIST:JOBPAK,MGR.T6132481 CPU sec. = 18720. elapsed min. = 8676. TUE, JUN 16, 2005, 10:39 AM.

Log #28 file #59, files1/A.14746.897498220, #J8597, $STDLIST:JOBPAK,MGR.T61519 CPU sec. = 402. elapsed min. = 35. WED, JUN 10, 2005, 10:00 AM.

See also

FIND, LOG



SET

This command is used to switch various LIST command display options on and off.

Syntax

SET <option>

Operation

The SET command controls the information JobRescue displays when the LIST command is entered in Line mode.

The <option> entry is one of the following parameters: [FCTL|NOFCTL], [CCTL|NOCCTL] or [PCL|NOPCL]. (For more information, refer to “Line mode” in this chapter.)

This command represents the carriage control codes in the first byte position as an octal value.

Example

>> SET CCTL

See also

LIST



SHOW

Displays information about examined $STDLISTs, within the current log.

Syntax

(1) SHOW [<job–name>] [;[BACKWARD] EXCEPTIONS] ] [ [OFFLINE] [OKAY] ][ [ALL] [IBM] [FINFO] [REPORTS] ](2) SHOW <#Jnnn>(3) SHOW <file–number>(4) SHOW @.@

Operation

The SHOW command tells JobRescue to display descriptions of examined $STDLISTs and IBM job listings. For details on keyword definitions, refer to Line mode in this chapter.

The [IBM] keyword tells JobRescue to display only those entries that it has determined to be IBM job listings.

The [FINFO] parameter displays the actual saved filename in the NSD account.

The [REPORTS] parameter displays the saved report information rather than the $STDLIST information.

The <#Jnnn> parameter, used in format (2) above, signals JobRescue to display only those entries that match the given job number (prefaced by the #J delineator).

The display includes the JobRescue file number, the job number, the logon ID in the form <jobname>,<user>.<account>, the number of lines in the file and the logoff information.

Command formats (1) and (2) shown above use the same display format. If format (3) is used, JobRescue will display more detailed information about the file. Format (4) will show all $STDLISTs within the current log.

• If the job listing is found to have exceptions, JobRescue displays both E and M (interpreted as exceptions and missing text) indicators.

• If the file is an IBM job listing, JobRescue displays IBM on the right side of the display, followed by the original spoolfile name.

• The <job-name> keyword is equivalent to the logon ID. If <Job-name> is not used, use a semicolon. When <job-namee> is specified, it must be the first parameter. If any other parameters are also entered, <job-name> must be delimited by a semicolon (;). The other parameters use a space delimiter.

• SHOW entered with no parameters, is equivalent to entering:

SHOW MYUSER.MYACCOUNT ; OKAY,EXCEPTIONS,IBM

Example

>>SHOW T61Will display 2 record(s).

File# Job# JobName User.Account #Lines Ex Logoff-at Elap. Cpu35 8495 JOBPAK MGR.T61 1556 20050410 0918 1015 3073

13935 J5766 JOBPAK MGR.T61 270 20040729 1219 1235 3167



In the second example shown above, only the job(s) with both exceptions and/or missing text strings will be displayed.

See also

OPEN, RETRIEVE, SHOWALL, TEXT

2 $STDLIST(S) Displayed Total 2250 6240Average 1125 3120

>>SHOW @.T61; EX0 $STDLIST(s) Displayed. Total 0 0

Average 0 0



SHOWALL

Searches for a job name throughout all log directories.

Syntax

SHOW [<job–name>] [;[BACKWARD] EXCEPTIONS] ] [ [OFFLINE] [OKAY] ][ [ALL] [IBM]

Operation

The SHOWALL command repeats the SHOW command, format (1), beginning in LOG 0 (the current day’s) and continuing through the last log available. This is a convenient way to search for a particular job when the day it ran on is not known.

The <job-name> parameter can be used alone or in combination with any of the other optional parameters.

For SHOWALL to be of practical use, spoolfiles must have been configured to be saved for more than one day, using Post-processing options, or Configuring job-specific values for specific jobs, as described in Chapter 3, “The CONFIGIX Program.”

The search always displays in an ascending log sequence, starting at LOG 0 and moving incrementally higher, and a descending date/time sequence.

Example

>> SHOWALL UPDATE,@.@

See also

LOG, SHOW

Configuration file commands: Configure RETENTION Management

Configure Global Values command: Post–processing options.



SHOWFOLDER

This command displays the folder structure for a given tree or branch.

Syntax

SHOWFOLDER [<folder-name> | @]

Operation

This command tells JobRescue to display the folder structure, starting with <folder-name> and all folders beneath it. This command shows how folders relate to others within the same branch structure. It displays the number of spoolfiles in each folder and the time the folder was last updated with a new spoolfile.

The <folder-name> parameter is optional. Use the name of the folder in quotes. If folder-name is omitted, the system displays all top level folders. Wildcards are not allowed, however using @ for the folder name displays the entire nested structure.

Example

>>SHOWFOLDER.FolderName---------* Count Latest----------*ALL-REPORTS 735 2005/09/04 09:54:20M.I.S. REPORTS 129 2005/09/04 03:27:53MANUFACTURING 538 2005/09/04 18:37:12SALES 68 2005/09/04 09:54:20

Example

>>SHOWFOLDER “SALES”.FolderName---------* Count Latest----------*SALES 33 2005/09/04 09:54:20..SALES ORDER 35 2005/09/03 23:33:09



SHOWLOG

Displays the date and time of each available Log.

Syntax

SHOWLOG [<log–number>]

Operation

The SHOWLOG command displays the date and time of each available Log directory. If the optional log number is entered, only the date and time of that Log directory is displayed.

For SHOWLOG to be of practical use, a value must have been entered in the Post processing options dialog in the CONFIGIX program. In addition, the Retention Management cycle must have been configured. For details, refer to Chapter 3, “The CONFIGIX Program.”

Example

>>SHOWLOGThere are 28 logs available.Log# From Date/Time To Date/Time0 WED, 2005/07/29 10:20:27–> present 1 TUE, 2005/07/28 00:00:16 –> WED, 2005/07/29 10:20:272 FRI, 2005/07/24 00:00:28 –> TUE, 2005/07/28 00:00:163 THU, 2005/07/23 00:00:23 –> FRI, 2005/07/24 00:00:284 WED, 2005/07/22 10:20:06 –> THU, 2005/07/23 00:00:235 TUE, 2005/07/21 00:00:23 –> WED, 2005/07/22 10:20:066 FRI, 2005/07/17 00:00:26 –> TUE, 2005/07/21 00:00:237 THU, 2005/07/16 00:00:25 –> FRI, 2005/07/17 00:00:268 WED, 2005/07/15 10:20:06 –> THU, 2005/07/16 00:00:259 TUE, 2005/07/14 00:00:25 –> WED, 2005/07/15 10:20:0610 FRI, 2005/07/10 00:00:24 –> TUE, 2005/07/14 00:00:2511 THU, 2005/07/09 00:00:24 –> FRI, 2005/07/10 00:00:2412 WED, 2005/07/08 10:20:06 –> THU, 2005/07/09 00:00:2413 TUE, 2005/07/07 00:00:25 –> WED, 2005/07/08 10:20:0614 FRI, 2005/07/03 00:00:21 –> TUE, 2005/07/07 00:00:2515 THU, 2005/07/02 00:00:21 –> FRI, 2005/07/03 00:00:2116 WED, 2005/07/01 10:20:05 –> THU, 2005/07/02 00:00:2117 TUE, 2005/06/30 00:00:25 –> WED, 2005/07/01 10:20:0518 FRI, 2005/06/26 00:00:19 –> TUE, 2005/06/30 00:00:25

See also

LOG

Configuration file command: Configure RETENTION Management

Configure Global Values command: Post–processing options.



SHOWDELETELOG

In Line mode, displays information about $STDLISTs that have been deleted from JobRescue.

Syntax

SHOWDELETELOG [ <job–name> [ OFFLINE] ]

Operation

The SHOWDELETELOG command tells STATUS to display descriptions of examined $STDLISTs that have been deleted from JobRescue. This command can be used to determine which file to restore from your backup media.

The display includes JobRescue file names, job numbers, logon IDs in the form: <job-name>,<user>.<account> and the logoff information and the deletion date.

When <job-name> is specified, it must be the first parameter. The OFFLINE keyword tells JobRescue to send the file to the printer.

For this command to be of practical use, you must have backed up your files to tape.

Example

>>SHOWDELETELOGWill display 24 record(s)..

Posix Base Filename Job# FileDes JobName User.Account Saved PurgedR.14783.897499216.cmp J8621 STDLOG JOBPAK MGR.T61 050610 001003R.15168.897548428.cmp J8621 STDLOG JOBPAK MGR.T61 050611 001003R.17108.897980441.cmp J8621 STDLOG JOBPAK MGR.T61 050616 001003R.18073.898153244.cmp J10488 STDLOG JOBPAK MGR.T61 050618 001003R.20025.898585252.cmp J10488 STDLOG JOBPAK MGR.T61 050623 001003R.21433.898844434.cmp J10488 STDLOG JOBPAK MGR.T61 0626 001003R.22850.899190046.cmp J10488 STDLOG JOBPAK MGR.T61 050630 001003R.32895.904028436.cmp J5833 STDLOG JOBPAK MGR.T61 050825 001003R.32897.904201234.cmp J5833 STDLOG JOBPAK MGR.T61 050827 001003R.32902.904633226.cmp J5833 STDLOG JOBPAK MGR.T61 050901 001003R.32907.905361642.cmp J5833 STDLOG JOBPAK MGR.T61 050909 001003R.33398.905966424.cmp J5833 STDLOG JOBPAK MGR.T61 050916 001003R.33747.906015639.cmp J5833 STDLOG JOBPAK MGR.T61 050917 001003R.34207.906102032.cmp J5833 STDLOG JOBPAK MGR.T61 050918 001003R.35617.906447663.cmp J5833 STDLOG JOBPAK MGR.T61 050922 001003A.35889.907258951.cmp J6 $STDLIST JOBPAK MGR.T61 051001 001003R.12702.954918023.cmp J5894 STDLOG JOBPAK MGR.T61 000405 000928R.13190.955004427.cmp J5894 STDLOG JOBPAK MGR.T61 000406 000929R.13650.955090839.cmp J5894 STDLOG JOBPAK MGR.T61 0407 000930R.14110.955177239.cmp J5894 STDLOG JOBPAK MGR.T61 000408 001003A.32893.969652055.cmp J5833 $STDLIST JOBPAK MGR.T61 000922 000926A.35854.969919826.cmp J5 $STDLIST JOBPAK MGR.T61 000925 000929R.35881.969951645.cmp J13 STDLOG JOBPAK MGR.T61 000926 001004R.35883.970124432.cmp J13 STDLOG JOBPAK MGR.T61 000928 001005

24 files(s) Displayed. STDLOG JOBPAK MGR.T61>> STDLOG JOBPAK MGR.T61



See also

LOG, SHOWLOG, RETRIEVE

Configuration program: Configure RETENTION Management.



STATS

Displays statistical information about job file sets.

Syntax

STATS [<job–name>]

Operation

The STATS command can be used to display statistical information about the jobs that are currently being stored in JobRescue. These statistical averages are based upon data available in the system that crosses log boundaries.

The STATS command searches all logs and shows matching entries and CPU time.

This command allows use of wildcarding with logon IDs. If only one part of the logon ID is used, it defaults to the account name portion; JobRescue assumes that the session and user names are @. If the user name and account are specified, JobRescue assumes that the job name is @.

Example

>>STATSDisplaying job set @,@.T61

.

Log# F# Job# Logon at Logoff at Elapsed Cpu Sec %Cpu #Lines Ex0 184 J18 20051005 1936 20051005 2002 26 18 1 1466 5 J7 20031001 0922 20031001 1020 58 29 0 193

2 Jobs displayed. Total 84 47 339Average 42 23 169

At the end of a STATS listing, the complete number of jobs is displayed and a total and average of each of the columns (for timing values and line numbers). All Logs are displayed when the STATS command is entered without a filename parameter.



TEXT

Opens an examined $STDLIST, report or IBM job listing.

Syntax

TEXT <file–number>TEXT <#J nnn>

Operation

The TEXT command opens the saved $STDLIST file, corresponding to either the file number or the job number displayed by the SHOW command.

You can use an open $STDLIST file in LIST or COPY operations.

Any files opened by you are indicated with an asterisk (*) next to the job number in the SHOW display. More than one user may have the same file open at the same time.

Example

>>SHOWWill display 1 record(s).

File# Job# JobName User.Account #Lines Ex Logoff-at Elap. Cpu184 J18 JOBPAK MGR.T61 146 20051005 2002 26 18

1 $STDLIST(s) Displayed. 26 18Average 26 18

>>

See also

COPY, FIND, LIST, OPEN, RETRIEVE, SHOW



VERSION

Displays the STATUS logon banner and the version number.

Syntax

VERSION

Operation

The VERSION command can be used to display the logon banner and version number of the STATUS program.



WIDTH

Changes the maximum display length for LIST and other commands that write to the terminal.

Syntax

WIDTH <print–width>

Operation

By default, STATUS sends a maximum of 142 characters to the terminal on a single line. However, this may cause wrap-around type on long text lines.

The WIDTH command allows this number to be changed by entering a positive number for print width.

WIDTH does not affect the COPY command.

Example

>> WIDTH 79>> W 67

See also

COPY, LIST



Report modeWhen Report mode is accessed in the STATUS program, $STDLISTs and individual reports can be viewed using a user interface called the Viewer. Enter the STATUS program by typing:

status.jpak.nsd

To enter Report mode, at the Line mode prompt, type:

>> report

Optionally, enter Report mode on the MPE command line by typing:

STATUS.JPAK.NSD—R

To quit Report mode, press F8-EXIT VIEWER.

Viewer—folder tree

When the Viewer initially opens, the JobPak folder tree appears:

The folder tree contains a hierarchical listing of all of the folders containing the reports currently in the system. Refer to the “Configuring folder organization” section in Chapter 3, “The CONFIGIX Program.”

Function buttons appear at the bottom of the Viewer screens, providing a shortcut method to execute commands. These buttons correspond to the F1-F8 function keys on the keyboard. (Some of these buttons remain undefined.)



If the folder tree is very large, press F1-FIND FOLDER to quickly locate a particular folder.

To display just the top-level folders, select F4-COLLAPSE ALL. The total number of spoolfiles stored in the JobPak folders appears on the right-hand side of each top-level folder.

To re-display all of the folders in the JobPak folder tree, select F2-EXPAND ALL.

To expand one section or branch of the folder tree, highlight a folder as shown below and press F3-EXPAND BRANCH.



To view the subfolders in any particular folder, highlight the parent folder and press ENTER.

Updating folder tree

If you have been in Report mode for some time, there may have been changes to the configuration that have not been recorded. To update the folder tree and create a current list of folders and reports, press F6-REFRESH DISPLAY.

Viewer configuration options

In Report mode, the screen configuration can be changed for individual viewing. At the Viewer folder tree screen, select F5-CHANGE CONFIG. The Screen Configuration Options dialog box appears:



Note: To access the Screen Configuration Options screen when viewing a report, press F6-Misc Keys.

To change the screen configuration, supply parameters as follows:

• Vertical scroll increment (#lines)—enter a number to specify how many lines to scroll through the report when using the UP and DOWN arrow keys.

• Horizontal scroll increment (#columns)—enter a number to specify how many columns of the report appear when using LEFT and RIGHT arrow keys.

• Maximum scroll to right edge (#columns)—enter a number from 80 to 264 to change the defined right-hand column scroll destination (defaults to 132).

• Automatic switch to HP 132-column mode—using Reflection or an HP terminal emulator, you can enter a Y to reconfigure to a 132-column screen width.

Screens will automatically switch between 80-column and 132-column mode. Rows do not change.

• Automatic screen dimension detection—enter Y to automatically calculate the rows and columns of the display and apply fit-to-window dimensions.



This feature automatically detects how many columns and rows the display has, and will then attempt to fit the information into the screen area, as opposed to the default 80-column x 24-row display.

• Initially explode all folder trees—enter Y to configure the folder tree to display all of the subfolders in the hierarchy.

• F4-user function key :XEQ filename—Reflection users can define the F4-User Key with an MPE file name.

Enter the name of the MPE :XEQ file to be executed via this user-defined function.

The first eight characters of the filename will appear as the label on the function key botton.

Report viewing

The number of reports a folder contains is displayed to the right of that folder on the folder tree as shown below.

To access a report, highlight the folder where the report resides and press ENTER. A listing of the reports in the selected folder is displayed, as shown below.



For more information, refer to “Viewing report generations” in this chapter.

Reports are sorted by File designation, Account name, User name, Job/Session, and time sequence (in descending order).

The following information is displayed for each listed report: the generation (version) count, the most recent generation (latest creation time), and the device on which the spoolfile originated.

Locating reports

If a folder displays an extensive list of reports, press F1-FIND REPORT to quickly locate a specific report.

Enter the file designator, job name, user name, account name and originating device, in that order, into the five fields that are displayed at the bottom of the list, as shown in the following example.



To list all the generations of a particular report, including page count and time of creation, highlight the report and press F3-EXPAND REPORT. The report generations are listed in descending time sequence, as in this example:



To re-display the original report listing, showing all of the report generations in the folder and the page count, press F2-EXPAND ALL. To display only the most recent generations (and the generation count), press F4-COLLAPSE ALL.

A tilde appearing next to an individual report listing indicates that page numbering within the report is approximate (no tilde indicates there is carriage control in those files), as explained below.

Viewing report generations

To view a particular report, highlight the report listing and press ENTER.



If the file has carriage control, demarcation lines will be displayed within the report indicating the beginning and ending of each new page. The example above shows a report with carriage control; however, sometimes a report without carriage control may also display an initial page indicator at the top, resulting from a form-feed command.

The status line, highlighted at the bottom of the Viewer screen, indicates the pages and lines relative to one. Line number one, indicating the top line, changes while scrolling up or down, using the keyboard arrow keys.

There are a total of 132 columns, with 80 columns for full-screen viewing. A circumflex (^) flags the left and right column numbers. While scrolling to the right or left, using the RIGHT and LEFT arrow keys, these column numbers will change. These parameters can be manipulated using the configuration options detailed in this chapter.

Report navigation

To navigate within a report, use the Page Up and Page Down keys on the keyboard (a page corresponds to a full-screen view, as opposed to a complete document page), or use the UP and DOWN arrow keys to move the cursor a line at a time.

The following table describes the function buttons at the bottom of the Viewer screen. Detailed procedures follow the table.

Name Key Description

MaxLeft F1 Aligns Viewer flush left to column 1 of report.



Line page controls

Press F2-Line Page Controls to access line navigation functions when viewing a report. The function button display toggles to the following selections:

F1-GoTo Line—enter a line number to view. The specified line displays at the top of the screen when you press ENTER.

F2-ShowLine Numbers—displays line numbers along the left-hand side of the page (offsets the text by eight positions). Toggle this function again to deactivate the line numbers.

F3-GoTo Page—enter a page number at the prompt to access a page of the report. If ENTER is pressed without entering a page number, the prompt disappears.

F4-Show Columns—displays column numbers, in increments of ten, at the bottom of the screen. Toggle this function again to deactivate the column numbers.

F6-Exit LinePage—exits the line page control functions and goes back to the basic Viewer functions.

F5 is undefined for the Line Page Controls.

String search

F3-String Search to find text in a report. The function button display toggles to the following selections:

F1-Enter FindText—at the prompt enter text to be found. Enter f or b to search forward or

backward from the current location.

F2-Find Next—find the next occurrence of text that has been specified by Enter FindText.

F3-Find Options—enter search parameters. The Search Configuration Options dialog box

appears:

LinePage Controls F2 Accesses line navigation functions.

String Search F3 Accesses text searching functions.

MaxRight F4 Moves to the value configured for max. scroll to right (refer to Viewer configuration options).

Head/Col Freeze F5 Locks heading and columns on display.

Misc Keys F6 Accesses miscellaneous configuration functions.

HELP F7 Displays help.

EXIT Report F8 Returns the display to the report list.

Name Key Description



Supply values in the fields as described below:

• Remove spaces during search—enter Y to remove spaces from a text string specified and the spoolfile text specified with Enter FindText, thereby speeding up the search.

• Match case during search—enter Y to specify the text search as case-sensitive to the specified text string.

• Search frozen heading area—enter Y to search the locked lines at the top of the screen. To define locked lines, refer to Heading and column freeze in this chapter.

• Left-most column to search—enter the number of the leftmost column to define where the search begins.

• Right-most column to search—enter the number of the rightmost column to define where the search ends.

To save the search configuration, tab to OKAY and press ENTER.

Press F6-Exit Search to toggle back to basic Report mode functions.



Heading and column freeze F5

When scrolling through long reports, it may be helpful to keep column headers in view at the top of the screen. To lock or freeze a heading or column in place, press F5-Head/Col Freeze. The function button display toggles to the following selections:

Key Description

F1–Heading Freeze Locks the report heading at the top of the Viewer screen, and toggles the function button display to the following:

F1–Increase HeadLock Incrementally adds horizontal heading freezes from the top down. One or more rows can be added to the beginning of the page/column orientation, and the heading configuration can be viewed separately when exiting Heading Freeze.

F2–ShowLine Numbers Shows line numbers along left-hand side of page and offsets the text by eight positions. Toggle again to deactivate.

F3–Remove Last Lock Incrementally removes a headlock, starting with the last freeze applied.

F4–Show Columns Displays numbers in increments of ten, at the bottom of the screen, indicating the column numbers.

F5–Lock a Line Freezes text in a line. At the prompt, enter a line number to freeze, and press ENTER. The line appears at the top of the screen.

F6–Exit HeadFreeze Toggles back to the Heading/Col Freeze functions.

F3–Column Freeze Locks columns vertically, rather than horizontally, and toggles the display to the following function buttons:

F1–Add Segment Concatenates selected columns and automatically creates a separate view of the selection, which can be viewed by exiting Column Freeze. When this function is selected, the column numbers (read vertically, beginning with the numeral 10) are automatically displayed at the bottom of the report, as shown below:

1111111111222222222233333333344444444555555555566666123456789012345678901234567890123456789012345678901234567890123

--------------------------------------------------------------

At the prompt, enter a beginning column number and a delimiter (space or comma) and an ending column number. The delineated columns are highlighted when ENTER is pressed. Exit Column Freeze to see the specified segment displayed.

F2 ShowLine Numbers Shows line numbers along the left-hand side of the page, offsetting the text by eight positions. Toggle F2 again to deactivate.

F3 Remove Last Segment Removes highlighted columns from the report display that was added with Add Segment.



To return to the basic viewer, press F6 Exit Freeze.

Miscellaneous keys F6

When viewing a report, press F6-Misc Keys, to toggle the function button display to the following selections:

F1-Change Config—displays options for changing the report viewing configuration, as described previously in Viewer configuration options.

F2-CopyTo PC File—saves a portion of a report to a PC file. e3000 files can be downloaded to SheetMate or Monarch software packages (or Notepad).

To do this, you must be in a Reflection environment. Enter the beginning and ending page numbers, select OKAY and press ENTER.

When the Save File dialog box appears, enter a filename and select Save. The file is then copied to your PC environment.

F3-Print by Page—prints screen dialog directly from the e3000 environment data, as shown:

F4 Show Columns Displays numbers in increments of ten, at the bottom of the screen, indicating the column numbers.

F6 Exit Column Freeze Toggles the buttons back to the Head/Col Freeze functions.

Key Description



Input for Print by Page is as follows:

• Local printer or system spooler—enter an L to specify a direct printer connection or printing via a network connection; or enter S to send the file back into the e3000 spool system, for printing.

• Send init escape sequence if system spooler—enter an N if a laser printer is not being used and initialization sequences do not need to be sent.

• Keep HP2680 ENV file data if system spooler—if the file was originally spooled to an HP2680 printer, enter a Y to keep the original 2680 commands, or an N to strip them out before printing.

• Portrait or landscape—enter a P or L to specify either a vertical or horizontal paper orientation, respectively.

When specifying orientation and pitch, there is an option to specify Landscape, Portrait or Compressed (see next item).

• Compressed or default print pitch—enter a C or D to specify the horizontal measurement of the number of characters per linear inch.

If a compressed font is already configured in the printer, the default and compressed print pitch will produce the same result.

• :FILE command for system spooler destination—in an e3000 environment, enter the MPE :FILE command that the file is to be printed to.



• Beginning page to print and Ending page to print—enter a value range for the beginning and ending pages.

If using Reflection, before processing this configuration, activate the print bypass feature to prevent any escape sequences from being processed. To do this, from the Terminal menu, select Printer. The Printer setup dialog box appears:

Check the Bypass Windows Print Driver option and then tab to OK and press ENTER.

Optionally, from the menu at the top of the Reflections window, select File. Select the Print Setup command. Highlight or mark the Bypass Windows Print Driver option. Also, highlight or mark the Disable Printer Translation option. Deselect (uncheck) the Auto Form Feed option.

In the Print by Page form, tab to OK, and press ENTER to process the printing configuration for the current job.

F4-User Key—can be configured as a user-defined key; the button on the display will change to reflect the label you specify. Refer to Viewer configuration options in this chapter.

F5-Indexing—finds the index values that were extracted from the current file previously saved with a Pattern indexing configuration, as detailed in the Configuring job-specific values section of Chapter 3, “The CONFIGIX Program.”

When this function is selected, a list box is displayed that shows the word, line and column entries of any index values in the report currently being viewed.



The indexes will be numbered, in relation to how many indexes a particular report has. The index name, next to the index number, is assigned in the Description field of the Pattern Indexing configuration, as detailed in Chapter 3, “The CONFIGIX Program.”

To find a value, highlight it in the list and press ENTER. The cursor locates that column and line in the report.

If a report has more than one configured index, press F1-Switch Index to toggle the display to the other index lists (i.e., Index #1, Index #2, etc.).

If an index list is particularly long, press F3-Go To Value, which prompts for a value range and quickly accesses the specified range, as shown below using the example Index #1 Account Number:



At the bottom of the index list, in the Enter Search Value field, type the desired word, line and column (with a space between each entry) and press ENTER; the specified value range is highlighted.

F6-Exit Index—toggles back to the Miscellaneous Keys.

F6-Prev Keys—toggles the display back to the basic Viewer functions.

Select F8-Exit Report to return to the listing of reports in the currently selected folder.

Note: To re-index a report that has been previously indexed, use the JPAKCOM command, REINDEX. (Go to Chapter 5, “The JPAKCOM Program,” for more information.)


Chapter 5 The JPAKCOM Program

JPAKCOM is an interactive program to assist in managing the operation of JobRescue. JPAKCOM commands instruct the JobRescue batch job to perform certain functions. For example, JPAKCOM can be configured to terminate JobRescue and allow it to log off.

Note: You must have SM or OP MPE (administrator) capabilities to use JPAKCOM.

Running JPAKCOMJPAKCOM can be run from any account on the system.

Enter the following command syntax, to access the JobPak prompt:

:JPAKCOM.JPAK.NSD

The following JobPak prompt appears:

JobPak Comm 6.1 (c) 1998 NobixWED, JUL 29, 2005, 3:16 PMJobPak:



JPAKCOM Commands

Command Function

EXIT Exits from JPAKCOM

MPE Directs the JobPak batch job to execute an MPE command.

PROCESS Directs JobRescue to reprocess an examined spoolfile.

REINDEX Reconfigures existing index values in a report.

RESUME Resumes JobRescue examination after suspension.

STOP Directs JobRescue to stop running and log off.

SUSPEND Directs JobRescue to suspend examination.

This chapter describes the function and syntax for each of these commands.



EXIT

This command closes the JPAKCOM program.

Syntax

EXIT

Operation

When this command is entered at the JobPak: prompt, the JPAKCOM program is terminated and you are returned to MPE.

Example

>> EXITEND OF PROGRAM.MPE:



MPE

This command directs JobRescue to execute an MPE command from within the JobPak job.

Syntax

MPE: <command>

Parameters

Any valid executable MPE command. It must be separated from the MPE keyword by a colon (:).

Operation

This command allows you to instruct JobRescue to execute the command from within its running job; as a result JobRescue does not have to be stopped and restreamed.

This may be valuable when it is necessary to redirect an EXCPTLST file to a different device than the default LP.

Example

Jobpak: MPE: FILE EXCPTLST;DEV=LASERFROM/JOBRSQ,MGR.NSD/MPE COMMAND HAS BEEN EXECUTED

Note: This command requires SM capability. OP users may not execute the :MPE command.



PROCESS

This command directs JobRescue to process a spoolfile.

Syntax

PROCESS <spoolfile–number>

Parameters

The <spoolfile-number> of a spoolfile in the spool system is the #0nnn number assigned by MPE when the spoolfile was created. This parameter is required.

Operation

JobRescue typically examines all READY spoolfiles.

The error message

REPORT #0nnn, FileDes FROM JOB #Jnnn NOT PROCESSED

indicates that JobRescue found an error in the job that created the indicated spoolfile and JobRescue is not going to examine it. You must determine whether the spoolfile is okay to print.

The PROCESS command can be used to process spoolfiles that have this disposition with JobRescue. This forces JobRescue to examine the report.

Example

JobPak: PROCESS 123FROM/JOBRSQ,MGR.NSD/ OKAY, REPROCESS 123



REINDEX

This command allows a previously indexed spoolfile to be re-indexed.

Syntax

REINDEX <filename>

Parameters

<filename> is the name of a saved spoolfile in the NSD account. The filename of the files stored in the NSD account can be displayed using the FINFO option in the STATUS program’s SHOW command. This parameter is required.

Operation

Any previously generated index values are deleted and new index values are developed, based on the current configuration.

Example

JobPak: REINDEX /NSD/files1/R.1234.567890FROM/JOBRSQ,MGR.NSD/ OKAY, REINDEX



RESUME

This command resumes spoolfile examination that has been suspended.

Syntax

RESUME

Operation

The RESUME command instructs JobRescue to begin examining spoolfiles again.

RESUME will have no effect unless JobRescue is currently suspended.

Example

JobPak: RESUMEFROM/.../$STDLIST EXAMINATION HAS RESUMED.

See also:

SUSPEND command



STOP

This command stops the JobPak batch job and causes it to log off.

Syntax

STOP

Operation

To stop JobPak, issue the STOP command.

Once the STOP command is given, JobPak ignores any other commands. This is the orderly way to stop JobPak.

If possible, do not use the MPE command ABORTJOB.

Example

JobPak: STOPFROM/../STOP COMMAND RECEIVED, WAIT FOR TERMINATION MESSAGE.



SUSPEND

This command directs JobRescue to suspend spoolfile examination.

Syntax

SUSPEND

Operation

Use the SUSPEND command to direct JobRescue to continue running, but not perform any spoolfile management (such as the examination of $STDLISTs).

The suspension remains in effect until the RESUME command is entered.

Example

JobPak: SUSPENDFROM/.../JOBRESCUE $STDLIST EXAMINATION IS SUSPENDED.

See also:

RESUME command


Chapter 6 The STDLOG Report

A STDLOG report contains information about the most recently examined $STDLISTs.

JobRescue keeps $STDLISTs online for a minimum of one day or until the next Retention Management cycle produces a STDLOG report. The STDLOG report contains all jobs listed during the period of time since the last cycle. The period of time in which a set of $STDLISTs is saved is referred to as a “log.”

Each time $STDLISTs are placed on the STDLOG report, a new set of $STDLISTs becomes available as the current set. The current set of $STDLISTs is placed in the STDLOG report at the next Retention Management cycle, as specified in the configuration program. Refer to the Chapter 3, “Configuring retention management” section in Chapter 3, “The CONFIGIX Program.”

STDLOG configurationA STDLOG report contains three sections of information about the most recently examined $STDLISTs.

• Section I Index of all jobs examined.

• Section II User-defined indexes.

• Section III Text portion of the $STDLISTs.

The indexes in Section I help locate text in Section III quickly, which becomes more important as the level of batch activity increases.

The index references in Sections I and II specify where to find the text in Section III; this may include page numbers.

For a sample STDLOG, refer to Appendix C, “Standard Log Reports.”



The format of the STDLOG report is controlled via the CONFIGIX program. For more information, refer to Chapter 3, The CONFIGIX program, Configuring reporting.

Section I

The following fields appear in Section I of the STDLOG report:

Field Name Description

(E) and/or (M) Exceptions indicator

JobName The name, user.account of the $STDLIST

Job# The MPE assigned job number

Page The page this job is found on in Section III.

Examined At At Date and time JobRescue examined it

Logged On At Date and time the job logged on.

Logged Off At Date and time the job logged off.

Run Min. Elapsed minutes the job ran.

CPU Sec. CPU seconds consumed by this job.

An exceptions indicator in the left-hand column of section 1 tells whether an error occurred, or whether JobRescue generated an automatic copy of the $STDLIST when it was examined as follows:

• E—Indicates JobRescue found text lines that matched an Error string text entry as defined using the CONFIGIX program.

• M—Indicates text intended for the $STDLIST is missing, specified by a Missing error string text entry as defined using the CONFIGIX program.

For more information, refer to the “Configuring job specific values” section in Chapter 3, “The CONFIGIX Program.”

The sorting sequence of Section I is controlled by using the Sort Options command under Configure STDLOG Report on the Main Configuration menu. The sorting sequence can be formatted by job account, number, or name as detailed in Chapter 3, The CONFIGIX program.

IBM job listings that appear in the STDLOG report do not show logon/logoff and run-time information. An IBM designation and the original spoolfile name will appear instead.

Section II

Indexes can be created in Section II using the Index string definitions command under Configuring reporting on the Main Configuration menu, as detailed in Chapter 3, “The CONFIGIX Program.”

The heading of each index page in Section II contains the name of the index in the upper left-hand corner. JobRescue picks up the word following the word or phrase indexed, and lists it as the Parameter, in the body of the index page. The page number or numbers where it



appears in Section III, are displayed next to the Parameter word. (See the example in Appendix C, “Standard Log Reports.”)

Each index name is printed on a separate page in Section II. If there are no occurrences of a specified index on a page, that page is not listed or printed.

The default configuration is supplied with index references for the :RUN and :FILE commands. Refer to the “Job-processing options” section in Chapter 3, “The CONFIGIX Program.”

Section III

Each $STDLIST in Section III begins at the top of a new page, and every page contains a page number. The heading contains the job identification in the upper left-hand corner, allowing the report to be easily examined.

JobRescue removes all the carriage controls which occurred in the original $STDLISTs; this prevents unnecessary paper waste.

Printing specific accountsThe STDLOG report is produced when a file named MERGE.PUB is executed; this XEQ file prints a single STDLOG report. The program STDLOGR. is run from this file to produce the report.

Typically, MERGE.PUB is run at the end of a configured retention management cycle (as described in “Configuring Retention Management” in Chapter 3, The CONFIGIX program). Once the new log has been created, and the current $STDLISTs are in what is now Log 1, STDLOGR will be run with a log number of 1.

The XEQ file, MERGE.PUB, appears as:

FILE STDLOG;DEV=LPSTDLOGR.PUB –indexonly 1 @ @ @

If a printed copy of the STDLOG report is not required, comment out the STDLOGR command in this file (which can be modified with a text editor).

Note: The STDLOGR.PUB file is referenced here, rather than the STDLOGR.JPAK file.

To use the info=”” style syntax, use the STDLOGR.PUB XEQ file, rather than STDLOGR.JPAK.

The STDLOGR.PUB file appears as:

anyparm parmsstdlogr.jpak.nsd;info=“!parms”

For different versions of a STDLOG report, you can add the applicable STDLOGR commands to this file with required and optional arguments (entered on one line), delineated as follows:

STDLOGR.JPAK.NSD [–indexonly|–exonly] <log#> <jobname> <user> <account>

The required arguments to the command line are:

• <log#>—corresponds to the same log numbers as displayed by the SHOWLOG command in the STATUS program.

• <jobname>, <user> and <account>—can be explicit, or used with pattern matching.



For example, if you were running the report for just a “FINANCE” account, you would enter the following syntax:

stdlogr.jpak.nsd;info=“1 @ @ finance”

Note: Comparisons are not case-sensitive.

The optional arguments to the command line are –indexonly and –exonly, as follows:

• –indexonly specifies that only Section I of the report is printed and the page numbers all appear as notext.

• –exonly specifies that all jobs appear in Section I, but the text appears in Section III for only those $STDLISTS that have exceptions. Jobs that do not have exceptions appear with notext for a page number in Section I.

A typical command line would appear as follows:

stdlogr.jpak.nsd;info=”–indexonly 1 @ @ @”OR

stdlogr.jpak.nsd;info=“–exonly 1 @ @ @”

The program can be run from any account that has Read access to the JPAK.NSD group. This should only be MGR.NSD and those users with SM capability.

STDLOGR writes its report to a file named STDLOG. A FILE command can be used to redirect this report, such as:

FILE STDLOG;DEV=LP

Producing microfiche reports

If reports are to be produced on microfilm, modify the MERGE.PUB.NSD file, shown below, by uncommenting the comment lines in the file beginning with "while FILE-EXISTS" and ending with "stdlogr.pub 1@@@".

file stdlog;dev=lpstdlogr.pub –indexonly 1 @ @ @setvar FNUM 0setvar FILE_EXISTS truesetvar FNAME " "comment to generate a microfiche copy of the stdlog reportcomment uncomment the following lines:commentcomment while FILE_EXISTScomment setvar FNUM FNUM+1comment setvar FNAME "FICHE"+str("000",1,3–len("!FNUM"))+"!FNUM"comment setvar FILE_EXISTS finfo(FNAME,0)comment endwhilecommentcomment file stdlog=!FNAME;cctl;dev=disc;disc=100000;savecomment echo STDLOG is being written !FNAMEcomment stdlogr.pub 1 @ @ @commentcomment the following lines will capture the stdlog



comment report and process it. This will allow youcomment to view it in status if Electropage is enabledcomment and you define "stdlog" in Report Specific Values.Commentpurge readback,temp >$nullfile readback;temp;msg;nocctlsetvar highest_dfid 0listspf O@;seleq=[filedes=stdlog and jobnum=#j!hpjobnum] >*readbacksetvar stayinloop truewhile stayinloop

input aline < readbacksetvar beginchars str(aline,1,5)if beginchars = "INPUT" thensetvar stayinloop false

elseif str(aline,1,2) = "#O" thensetvar strdfid str(aline,3,7)

setvar testdfid !strdfidif testdfid > highest_dfid thensetvar highest_dfid testdfid

endifendif

endwhileif !highest_dfid > 0 then

process.jpak !highest_dfidelse

echo There is no STDLOG to process.Endifpurge readback,temp >$nulldeletevar highest_dfiddeletevar stayinloopdeletevar strdfiddeletevar testdfiddeletevar alinedeletevar begincharsdeletevar fnumdeletevar fnamedeletevar file_existscomment

The FILE command for STDLOG is contained in the MERGE.PUB.NSD file.

Caution: Any changes made to this file will be overwritten when JobRescue is updated to the next version.

Changing reporting defaults

The following Configuration setups are detailed in Chapter 3, “The CONFIGIX Program.” They are used to alter the default reporting conditions.



Setup Description

Index string definitions To create a user-defined index in STDLOG (accessed via Configure STDLOG Report)

Sort Options To create a separate index for each of the sort options

Misc System value To change the name at the top of the STDLOG report

Sort Options Index page sorted by account

Sort Options Index page sorted by job number

Sort Options Index page sorted by job name



Chapter 7 Deferring $STDLISTs

$STDLISTs that are closed and immediately printed cannot be managed or examined by JobRescue. To ensure that $STDLISTs do not print, they must be deferred before they are closed by the system. JobRescue defers $STDLISTs automatically; this capability has been included as part of the JobPak job control.

It is not necessary to manually defer $STDLISTs in JobRescue, since the program automatically does this by setting a priority of zero when the spoolfile closes. Spoolfiles initially exhibit whatever the priority was set to, the default priority being 8, and then change to 0 at logoff or when files close. JobRescue retains the original priority.

After examining a file, JobRescue automatically restores the original priority, or deletes the spoolfile, depending on the JobRescue configuration.

The JPEnable command syntax activates the deferral process, ensuring that JobRescue will continually be able to examine spoolfiles.

Chapter 8 Advanced Features

This chapter contains information for advanced handling of $STDLISTs, :XEQ scripts, Exception Lists, and Action Control Sheets.

Delay $STDLIST examinationMPE procedure exits notify JobRescue when a new READY state spoolfile arrives in the queue. These programs immediately examine new spoolfiles for processing. To delay when JobRescue examines spoolfiles, place the DELAYEXAMSECS variable in the JOBPAK.JPAK file.

Syntax—

!SETVAR DELAYEXAMSECS #####

Where ##### is a number between 1 and 10,000 representing seconds for delay.

In the JOBPAK.JPAK file, place this line with other SETVARs prior to the command line JP02SXL.JPAK.

Special :COMMENT linesJobRescue usually ignores any comment lines it finds in $STDLISTs. However, a special comment line can be entered in job control to control the actions of JobRescue. These special comments control the examination phase by instructing JobRescue to skip over certain portions of the $STDLIST.

The text of the special comment line is important; however, it does not matter whether it is in upper- or lower-case characters. Spacing is not important, because JobRescue removes all spaces before it checks the comment line, but the words must be in the correct order.



Controlling text examination

With comment line commands, JobRescue can be instructed not to check for errors in certain portions of the $STDLIST. This also means that JobRescue does not look for any text defined as a Missing error string text entry in the configuration, as described in the “Customizing error detection” section in Chapter 3, “The CONFIGIX Program.”

JobRescue stops examining the spoolfile when it sees the following comment line:

:COMMENT JOBRESCUE EXAM STOP

Examination does not resume until JobRescue sees the comment line:

:COMMENT JOBRESCUE EXAM START

JobRescue continues examining the file until either another comment tells it to stop, or the end of the file is reached.

This allows you to block out portions of the $STDLIST JobRescue examines. You might want to do this if you know that these portions can cause JobRescue to calculate that there is a problem, even if there is not.

No matter what comment lines are used, JobRescue always saves the entire $STDLIST on disc.

Warning: Do not use these special comment lines if the job processing option, Follow MPE :IF commands in $STDLISTs, is also used. Refer to the “Configuring job-specific values” section in Chapter 3, “The CONFIGX Program.”.

Contents of MPE :XEQ scripts

To facilitate parameter passing and substitution, a common PARM header line must be used in all :XEQ files initiated by JobRescue (and ElectroPage).

It is important to note that there may now be multiple spoolfiles processed at the same time, which can require some coordination of variable name usage. This is due to a single job (JobPak) performing all the spoolfile processing, and MPE’s feature of sharing variable names between multiple processes running in the same session. Be aware that once variables have been assigned, they are not deleted at the conclusion of the :XEQ file being run, and they may tend to remain on the system until the termination of the JobPak job.

It is recommended that any variable names that may be assigned during the execution of a script have the Dfid number of the spoolfile being processed incorporated into their name, thus making them unique. Also, the :DELETEVAR command should be executed referencing any names assigned during the operation of the script.

The required PARM header line is in a file named PARMLINE.JPAK and can be copied into any :XEQ file of your design. It appears as:

PARM Dfid ExCnt MissingCnt JobPreFix JobNo FileDes=“”JobName=“” &UserName=“” AcctName=“” ElapMin CpuSec DateLogon=“” &TimeLogon=“” DateLogoff=“” TimeLogoff=“” JobPakFname=“”

The formats are as follows:

Format Description

Dfid Number portion only, no leading #O



Action control sheetThe Action Control Sheet (ACS) is printed as the last page or pages of the Exceptions List (EXCPTLST). This page can be configured to look any way you like.

The ACS is a document that data-processing personnel can use to record the occurrence of jobs found to have an exception. This document can be filed, or it can be used for later reference about a problem job.

The format of the ACS is stored in a file named OPACTION.PUB.NSD. JobRescue reads this file when it prints the EXCPTLST, and then appends it to the Exceptions List. OPACTION should have a minimum record length of 80 characters and a maximum of 132 characters. This file can be modified with any text editor. Keep the records unnumbered.

OPACTION may have up to 60 lines on each page; therefore, an OPACTION file containing 65 lines of text will produce a two-page ACS. The first page will have 60 lines and the second page will only have five lines.

JobRescue shifts lower-case text in the OPACTION to upper-case and converts ASCII control characters to spaces.

ExCnt Number of exception messages found. Zero if no exceptions

MissingCnt Number of missing messages expected. Zero if no missing messages

JobPrefix One of "#S"', "#S", "#J" or "#J"'

JobNo Job/Session number of the spoolfile’s creator. No leading "#S" or "#J"

FileDes File designator (spoolfile name) of the file being processed.

JobName Job or session name of the spoolfile’s creator

UserName User name of the spoolfile’s creator.

AcctName Account name of the spoolfile’s creator

ElapMin Elapsed minutes that the job (if a $STDLIST) ran

CpuSec CPU seconds accumulated during job (if a $STDLIST)

DateLogon Date that the job (if $STDLIST) logged on; format YYMMDD

TimeLogon Time that the job logged on; format HHMMSS

DateLogoff Date that the job logged off; format YYMMDD

TimeLogoff Time the job logged off; format HHMMSS

JobPakFname The name of the file as saved in the NSD account

Format Description



Substitution values

Variable names can be entered in the OPACTION file. JobRescue will substitute working values for these names. There are twenty-six variable names supported. The following list shows all the variable names and their replacement values.

Variable name Replacement Value

$NAME Spoolfile creator’s name, 8 chars

$USER Spoolfile creator’s user, 8 chars.

$ACCT Spoolfile creator’s account, 8 chars

$COMPANY Value of the $NAME command

$JOB Job/session number, format #Jnnn

$DATELINE Current date and time, 27 characters

$DATE Current date, format-21NOV05

$TIME Current time, format-22.35

$XCOUNT Number of exceptions found

$XLINE01 Text of the first line to have an exception

$XLINE02 Text of the second line to have an exception

…

$XLINE10 Text of the tenth line to have an exception

$CPU CPU seconds consumed by the job

$ELAPSED Elapsed minutes of the job

$LOGONDATE Logon date of the job, format-21NOV05

$LOGONTIME Logon time of the job, format-22:57

$LOGOFFDATE Logoff date of the job

$LOGOFFTIME Logoff time of the job

$OFILE Examined spoolfile number, #Onnn

$FNAME Name of the spoolfile or report

All replacement values are left-justified with trailing spaces.

Note: These variables can be used to insert customized information.

Additional alterations

The form design and page layout of the ACS can also be modified.



One way to do this is to create a file named OPCTL.PUB.NSD. JobRescue will dump this file to the EXCPTLST spoolfile immediately in front of the OPACTION file. OPCTL can contain control characters that send commands to the printer. For instance, this file can be used to change the character set, font type, or font rotation.

OPCTL must have a record length equal to or less than 132 characters. All characters in each record are written to EXCPTLST, including trailing spaces. JobRescue does not perform any character translation on the OPCTL file.

Since JobRescue writes OPCTL to EXCPTLST immediately after the $STDLIST text and immediately before OPACTION, this file can be used creatively to design a useful Action Control Sheet. OPCTL lets the text portion of the EXCPTLST look different from the ACS.

Sample action control sheet

The following page shows an editor listing of the OPACTION file before any translation takes place.

$DATE $COMPANY $TIMEJOBRESCUE

OPERATOR ACTION CONTROL SHEET

JOB NUMBER: $JOBNAME $NAME,$USER$ACCTLOGON: $LOGONDATE,$LOGONTIMELOGOFF: $LOGOFFDATE,$LOGOFFTIMEELAPSED: $ELAPSEDCPU: $CPU

RECEIVED BY:_____________________________________________REPORTED BY:____________________________________________

NUMBER OF EXCEPTIONAL TEXT LINES FOUND FOR $NAMR IS $XCOUNT. PROBLEMS FOUND WERE:

$XLINE01$XLINE02$XLINE03$XLINE04$XLINE05$XLINE06$XLINE07$XLINE08$XLINE09$XLINE010*****************************PROBLEM SOLUTION*******************************

PROBLEM TYPE:_____1-HARDWARE, 2-SYSTEM SOFTWARE, 3-OPERATIONS4-APPL. SOFTWARE, 5-COMMUNICATIONS, 6-OTHER

CAUSE OF PROBLEM:____________________________________________________________________________________________________________________________________WAS AN ON-LINE SYSTEM DOWN AS A RESULT OF THIS PROBLEM?_________(Y/N)IF SO, HOW LONG WAS IT DOWN (HOURS:MINUTES________:_________

****CORRECTIVE ACTION AND TIME TO FIX THE PROBLEM(S)****___________________________________________________________FIXED BY:_____________________WHEN FIXED_____________________(C) COPYRIGHT 1998, NOBIX $DATELINE



Note: The OPACTION file supplied with JobRescue is similar to the above example.


Appendix A The AutoDial Program

The AutoDial program provides JobRescue with access to an auto-dialing modem. AutoDial can tell the modem (or other automatic calling unit) to dial a pager number to alert computer personnel that a particular job has an error. AutoDial can dial different numbers for different jobs; this can be helpful when different people are responsible for these jobs and/or systems.

AutoDial must be run from a JobRescue script file. These are specified as MPE :XEQ files, described in Chapter 3, “The CONFIGIX Program,” and Chapter 8, “Advanced Features.”.

Most commonly, AutoDial would be run from the script file designated to be performed when an exception is detected.

Before AutoDial can be used, a job and dialing sequence cross-reference file must be defined. This file should be named PHONE.PUB.NSD. This file is a simple ASCII file which can be built with any suitable text editor. The file must be unnumbered and no longer than eighty (80) characters in record length. The PHONE file contains a list of job names and the associated phone numbers which should be called if there is an error. Wildcards may be used to match job names.

When AutoDial is run from a command file during $STDLIST examination, it is supplied with the job's logon ID. AutoDial uses this to match an entry in the PHONE cross-reference file.

Once it has made a match between the job ID of a failed job and an entry in PHONE, AutoDial opens the logical device of the modem or calling unit and writes the appropriate character sequence to this device. A coded numeric message can also be included that could be displayed on a pager, with the character sequence to be sent to the modem.

Many different types of modems are available, and their command sets may differ. Therefore, the correct character sequence must be defined in PHONE to initiate and complete the call for



your modem. The defined character sequence must match the command set of the autodialing modem or calling unit.

Nobix has supplied a PHONE file with JobRescue called PHONE.PUB.NSD. This file can be used as a template to build on.

Pager networksSince AutoDial is intended primarily for use in a pager network or environment, you should be familiar with the equipment to be used. This applies not only to the modem equipment at the site, but also to the equipment that the modem will be calling.

There are many different types of pager networks. AutoDial may be used with non-display pagers, or with more sophisticated numeric display pagers. Make sure that the pager network to be accessed is compatible with AutoDial.

Note: AutoDial is not recommended for use with audible voice or text pagers. Although it can access them, there is currently no mechanism to allow AutoDial to speak or to send text through a modem or autodialer.

Using AutoDialThere are many reasons why you might want JobRescue to contact a pager number when it detects a job error. For example, using AutoDial can reduce the time that data processing personnel need to be at or near the system console during normal production processing.

If JobRescue is being used in conjunction with a job scheduling system (such as the JobPak product JobQue), it may even be possible to have an unmanned computer room. This can be beneficial at night, or at other times when personnel are not available in the computer room. Since AutoDial can call different numbers for different jobs, simply have AutoDial contact the person responsible for a particular batch job or system and alert them to the presence of a batch error.

System setup

There is a sample MPE :XEQ file named ADXEQ.JPAK.NSD that can be used as a template (refer to “Enabling AutoDial” in this chapter). Modify the :FILE command that is in this file and reference the appropriate logical device number and the filename.

AutoDial accesses a modem through the MPE file system by opening the logical device that connects the modem to the computer system; therefore, you must enter a :FILE command to tell AutoDial the logical device number (LDN) of the modem that is to be used. The filename that AutoDial expects is PORT.

The command line should appear as:

:FILE PORT;DEV= LDN

where LDN is the logical device number of the modem.

PHONE fileThe PHONE file PHONE.PUB.NSD is a cross-reference of job names and dialing sequences. Any suitable text editor can be used to create this file. The PHONE file must be unnumbered and no longer than eighty (80) characters in record length.

Each record in PHONE defines a job ID. Each record is composed of two parts:

The first part is the job identification delimited by a semicolon (;).



The second part is the dialing sequence used for a matching job.

Wildcards can be used to match more than one job per line in the PHONE file.

PHONE record format

The format of each record is free-form. The job ID must appear to the left of the first semicolon delimiter. The dialing sequence begins immediately after the first semicolon on each record. Spaces in the first position after the semicolon become part of the dialing sequence. The record looks like this:

job–id ; dialing–sequence

For example:

PAYROLL,MGR.FINANCE ;ATDT5551212,,,,1234567890^M

As shown above, the job identification begins in column one, and there is a semicolon after the account name.

Job identification

The job ID is the logon ID of a job. It includes the job name, user name, and account name. The job ID uses standard MPE formatting, as in UPDATE,MGR.FINANCE and must start with the first non-blank character on each record.

The job ID can be entered in upper- or lower-case. Only ASCII letters and numbers and the MPE wildcard-matching characters can be used.

For example:

MYJOB,MGR.FINANCE;

The wildcard character “@” may be used. If any portions of the logon ID are missing, they default to the wildcard character “@”. For example, a job ID that matches all jobs would be specified as:

@,@.@ ;

AutoDial selects the first PHONE record that matches. If a matching job ID has not been defined in the PHONE file, then AutoDial will take no action for that particular job.

Dialing sequence

Enter the dialing sequence immediately after the first semicolon following the job ID. The dialing sequence may contain any valid ASCII characters. Upper- and lower-case are preserved in this portion of the PHONE record.

Caution: The complete dialing sequence must be on the same line as its corresponding job ID. Continuation lines are not supported.

Control characters in the dialing sequence

Some modems and autodialers require control characters to be sent to them to perform some type of action. Control characters can be defined by placing a caret (^) in front of the character. For example, if a carriage return is specified as a CTRL-M, this would be represented as ^M. A CTRL-B would be defined as ^B. To define the actual caret character itself, use two carets next to each other, as in ^^.



To instruct AutoDial to pause for a half-second, enter a dollar sign ($) into the dialing sequence. Dollar signs are not transmitted to the modem; therefore, they only cause AutoDial to pause. Additional dollar signs can be entered and placed next to each other. They may appear anywhere in the dialing sequence.

A sample dialing sequence might appear as:

job–id ;^M$$$ATDT555–1234,,,1234567890#^M

The above sequence performs the following tasks:

• The CTRL–M (^M) sends a carriage return to the modem.

• The dollar signs each initiate a half-second pause.

• The ATDT is the Hayes-compatible dialing command.

• The telephone number 555–1234 is sent to the modem. (Remember to add a 9 if the system requires it to dial out.)

• Three commas are sent to the modem. Since the Hayes default delay is two seconds per comma, the commas give the pager enough time to answer the ringing line.

• The number 1234567890# is sent to the modem. This number would be displayed on the pager.

• A CTRL–M (^M) or carriage-return is sent to the modem; this terminates the command.

Note: This sequence may not be applicable to your equipment. It is intended only as an example. Please check the modem manual to verify.

How the dialing sequence is sent

AutoDial sends the dialing sequence character by character, beginning with the first character after the semicolon. Autodial uses a separate FWRITE for each character.

AutoDial delays for a half-second after writing each character to the modem port. The delay is used because some modems cannot handle a faster rate. AutoDial is trying to act like a person typing through a terminal connected to the modem.

Note: AutoDial opens the modem logical device as a file. The line speed is not changed from the device’s MPE configured value. The modem port is set to the equivalent of term type 18. The port is opened for read/write access.

The dialing sequence should contain not only everything required to connect the modem t to the pager network, but also the information that must be sent to the pager equipment. In other words, the dialing sequence must contain the pager phone number and the number (if any) to be displayed on the pager itself.

If the modem requires a confirming carriage return before it will dial a number, be sure to include an extra CTRL–M (^M) in the dialing sequence.

Pager networks usually require a certain amount of time to answer an incoming call from the modem. Some networks answer on or before the first ring, while others answer on the third or fourth ring. Time must be allowed for the network to answer before sending a number that is to be displayed on the pager. Most autodialing modems allow a pause or delay character to be included in the dialing sequence. On some modems, the comma (,) or letter K tells the modem to pause for a predetermined amount of time. These pause characters



should be entered between the pager network phone number and the number that is to be displayed on the pager.

Note: Although most telephone networks allow pulse dialing, most display pager networks require tone dialing.

After the sequence is sent, AutoDial pauses for thirty seconds before it closes the logical device for the modem. This prevents the possibility of a premature hang-up on the modem, if control signals from MPE are dropped when the device is closed.

Enabling AutoDial

The ADXEQ template file appears as follows:

PARM Dfid ExCnt MissingCnt JobPreFix JobNo FileDes="" JobName="" &UserName="" AcctName="" ElapMin CpuSec DateLogon="" &TimeLogon="" DateLogoff="" TimeLogoff="" JobPakFname=""

COMMENT This is the execute file used for running the AUTODIALCOMMENT program. Modify the command line "setvar PORTLDN 21"COMMENT to the port you will use for your modem.

if !ExCnt = 0 and !MissingCnt = 0 thenreturn

endifecho AUTODIAL.XEQ !JobPreFix!JobNo BEG !HPDATEF !HPTIMEFsetvar cnt!Dfid 0

setvar stayinloop!Dfid truewhile stayinloop!Dfid

setjcw cierror 0continuebuild autolock>$nullif cierror = 0 then

setvar stayinloop!Dfid falseelse

pause 20setvar cnt!Dfid cnt!Dfid + 1if cnt!Dfid > 15 then

setvar Atime finfo("autolock",20)setvar Adate finfo("autolock",21)

echo !HPTIMEF In AutoDial loop > 5 Mins. Autolock was made !Adate !Atimesetvar stayinloop!Dfid false

endifendif

endwhilesetvar PORTLDN 21

file port;dev=!PORTLDNcontinueabortio !PORTLDN > $null

continueautodial.jpak;info="!JobName !UserName !AcctName"

continueabortio !PORTLDN > $null

purge autolockdeletevar stayinloop!Dfid

deletevar cnt!Dfid



echo AUTODIAL.XEQ !JobPreFix!JobNo END !HPDATEF !HPTIMEFsetjcw cierror 0

Modify this script file appropriately, as described in the System setup in this chapter, and then name it.

In the MPE :XEQ scripts configuration, list the filename as one of the :XEQ files that will be executed when spoolfiles are examined, as discussed in Chapter 3, “The CONFIGIX Program.” It can be referenced for either all files examined as a global XEQ, or for job-specific or report specific spoolfiles as a local XEQ in the configuration.

Ensure that PHONE.PUB.NSD has been defined. This file should only refer to jobs that require someone to be paged.

Selecting a modem

AutoDial may not be compatible with every modem. For example, there can be problems if the modem must have certain control signals supplied before it will go online with the computer system.

In some cases, the modem will not do anything until it is manually placed into terminal mode. This will not work with AutoDial, since no one will be present to do this.

Other modems will dial numbers; however, then they may wait for a second dial tone or carrier signal. If the proper signal is not received in time, the modem may hang up the phone line. Therefore, only pick a modem that can be controlled with characters placed in the dialing sequence.

Most Hayes-compatible modems will work well with AutoDial. These types of modems are easiest to use because they have the simplest dialing syntax.

The original HP Support Link modem is difficult to enable. The later release of the HP Support Link is a Hayes-compatible modem.

When accessed, most display pagers require tones to be sent to them, similar to the ones created by a push-button phone.

Note: To achieve the best results with AutoDial, Nobix recommends use of an HP modem cable, Part # 92219Q or equivalent.

AutoDial in test mode

There is a special TEST entry point included in AUTODIAL.JPAK.NSD that allows testing of AutoDial in a non-production mode.

In test mode, AutoDial does the following:

• Prompts you for a job name, user and account.

• Searches PHONE.PUB.NSD for a matching entry.

• If it finds a match, it will try to initiate a modem transmission.

• Echoes to your terminal exactly what it is sending to the modem.

This should help to enable AutoDial in your working environment.

Before trying AutoDial online, enter the appropriate :FILE command for the modem logical device. Type this on the terminal; enter the same information entered in the MPE :XEQ file.

To run AutoDial in test mode, sign on as MGR.NSD,PUB and enter the following:



FILE PORT;DEV=LDNAUTODIAL.JPAK.NSD –test

Note: The word test must be entered in lower-case letters.

AutoDial terminates automatically after dialing.

Error messagesThe following messages appear on the system console.

Message Description

AUTODIAL: CANNOT OPEN PHONE FILE AutoDial cannot open the PHONE.PUB.NSD file. This file contains job IDs and dialing sequences. Check to see that this file exists and that no lockwords or other security exists for this file.

AUTODIAL: CANNOT OPEN *PORT AutoDial cannot open the PORT file as defined by the :FILE PORT;DEV= LDN command line. Make sure you have specified the correct device and that the device is not in use by another process. Check that the modem is sending DataSet Ready to the e3000 logical device.

AUTODIAL: NO SPECIFIC RECORD FOUND IN PHONE

When executing AutoDial, it could not find a matching record in the PHONE.PUB file, which means AutoDial cannot perform its function for this spoolfile.

CANNOT OPEN PORT: DSR NOT AVAILABLE

Data Set Ready signal is not available from the modem; therefore, AutoDial cannot open communication to the modem. Check to ensure that DSR is always enabled on the modem or that the modem is connected to a non-modem control type LDN.


Appendix B The UNLOAD Program

The UNLOAD.JPAK.NSD program allows system administrators to make global changes to the configuration files contained within the CONFIGIX program. It performs the following tasks:

• Output an editable ASCII version of the configuration files.

• Backup the following five configuration files found in the JPAK group:

CONFIG

FOLDERA

FOLDERF

FOLDERR

FDISPLY

• Use the edited ASCII file as input to populate the five configuration files with data.

Any text editor that works with the e3000 can view or edit the ASCII file.

You must be very familiar with entries and syntax contained in CONFIGIX to edit this ASCII file. Refer to Chapter 3, The CONFIGIX program for information about CONFIGIX entries and syntax.

Create an ASCII configuration file

1 Logon to the system as MGR.NSD,PUB.

2 Enter the :FILE command specifying the name for the ASCII configuration file.

:FILE TEXTCNFG;SAVE;DISC=50000



3 Run the UNLOAD program using the ASCII configuration file name.

:UNLOAD.JPAK > *TEXTCNFG

UNLOAD creates an ASCII file named TEXTCNFG in the JPAK group.

Example—

1 0:GLOBAL:$GLOBAL:::::HEADER:NUM:02 0:GLOBAL:$GLOBAL:::::CHECKIF:NUM:13 0:GLOBAL:$GLOBAL:::::CHECKIF:NUM:04 0:GLOBAL:$GLOBAL:::::CHECKEOJ:NUM:15 0:GLOBAL:$GLOBAL:::::CHECKEOJ:NUM:06 0:GLOBAL:$GLOBAL:::::CONTOK:NUM:07 0:GLOBAL:$GLOBAL:::::STARTXEQ:TEXT:” “8 0:GLOBAL:$GLOBAL:::::ERROR:TEXT:”(CIERR”

Edit the ASCII configuration file

1 Use any text editor to view or edit the ASCII configuration file.

:EDITOR/T TEXTCNFG

2 When the edits are complete, keep the file.

/K TEXTCNFG,UNN/EXIT

The text editor saves the changes to the ASCII configuration file.

Rules for editing the ASCII file

• The ASCII file is structured into records and fields.

• Fields are delineated by colons (:).

• The first field, named Category, groups lines together that have the same category number. Category numbers range from 1 to 10.

• Category number definitions and descriptions are as follows:

Cat. # Contains Non-editable fields Editable fields

0 Global definitions Fields 2 through 9 Field 10, which follows TEXT: or NUM:

1 Job Specific definitions Fields 2, 3, 8, or 9 Fields 4, 5, 6, 7, and 10

2 IBM report definitions Fields 2, 8, and 9 Fields 3, 4, 5, 6, and 10

3 Report Specific definitions Fields 2, 8, and 9 Fields 3, 4, 5, 6, and 10

7 FOLDERF definitions (Top-level and Sub-folder)

Field 2, or a field with the value $FOLDERHEADER (Toplevel)

Fields 3 and 4 except if they have the value $FOLDERHEADER

8 FOLDERR definitions (Report folders)

Field 2 Fields 3 through 8



• Data in the fields following the :TEXT field are surrounded by double quotes (“) in the ASCII file. Changes to these fields must be within the double quotes.

• Changes to the ASCII file must meet the criteria stated in this guide for valid data in that specific field.

Backup the current configuration and load the edited ASCII file


2 Run the UNLOAD program using the output file name.

:UNLOAD.JPAK –LOAD < TEXTCNFG

The backup file name is CFGnnn.JPAK, where nnn is a 3-digit number that is automatically incremented.

The UNLOAD program creates a backup of the current configuration and loads the changes from the ASCII configuration file. The changes take effect immediately, even if JobPak is running.

Warning: UNLOAD does very little syntax error checking. If you load an ASCII file that has syntax errors, you might cause damage to the configuration files. If this occurs, refer to the Restore the backup configuration section.

Restore the backup configuration


2 Enter CHGROUP JPAK.

3 Enter LISTF CFG@,2.

4 Write down the number of the CFGnnn file with the highest number.

5 PURGE the files FOLDERA, FOLDERF, FOLDERR, FDISPLY, and CONFIG.

6 At the colon prompt, type UHAUL.PUB

This runs a script to access the backup configuration.

7 To the question "DO YOU WANT TO LOAD, UNLOAD OR LIST FILES?" enter UNLOAD.

8 To the question "ENTER THE NAME OF YOUR TRUCK," enter CFGnnn (where nnn is the number from step 4).

This is the file that contains the most recent configuration backup.

The system restores the backup to the configuration files.

9 FOLDERA definitions (Access security)

Field 2 Fields 3 through 6

10 FDISPLY definitions (Rarely occurs)

Do not modify

Cat. # Contains Non-editable fields Editable fields



Print a configuration report


2 Enter the :FILE command specifying the name for the ASCII configuration file.

:FILE TEXTCNFG;SAVE;DISC=50000

3 Run the UNLOAD program using the ASCII configuration file name.

:UNLOAD.JPAK > *TEXTCNFG

4 Enter the :FILE command specifying the name of the output file and device.

:FILE lp;dev=lp

5 Run the POSIX shell and the UNLOAD program specifying the name of the ASCII configuration file and output file command.

:SH.HPBIN.SYS /NSD/EXAMPLE/UNLOAD < TEXTCNFG > *lp

The system sends the report of the configuration to the specified file command.

Example—

UNLOAD.JPAK @ Wed Nov 18 14:30:37 PST 2005JobPak configuration

Type FileDes. Job/Ses User Account.Device Command Value 1GLOBAL CHECKIF NUM 0GLOBAL CHECKIF NUM 1GLOBAL CHECKEOJ NUMGLOBAL CHECKEOJ NUM 0GLOBAL CONTOK NUM 0GLOBAL STARTXEQ TEXT “ ”GLOBAL ERROR TEXT “(CIERR”


Appendix C Standard Log Reports

• A STDLOG report is produced whenever there is a scheduled Retention Management cycle, as described in the “Configuring retention management” section of Chapter 3, “The CONFIGIX Program.” The STDLOG consists of three parts:

• Section I—a list of the jobs contained in the report.

• Section I—user-defined indexes.

• Section III—the $STDLIST text.

The contents of the report are formatted with the Configure STDLOG report command described in the Configuring reporting section of Chapter 3, “The CONFIGIX Program.”

The reports can be produced either on microfiche or paper. For details, refer to “Printing specific accounts” in Chapter 6, “The STDLOG Report.”

The sample which follows depicts portions of a large STDLOG report.



This page will have the pdf of the report on it









STDCOPY listing

This report is printed whenever JobRescue makes an automatic copy of a $STDLIST, as directed by a Copy :FILE command entry in the Job processing options configuration. For details, refer to “Configuring job-specific values” in Chapter 3, “The CONFIGIX Program.”


Appendix D Exception List Reports

The Exceptions List is printed whenever JobRescue detects that a $STDLIST has an error or other exception.

The FILE command for EXCPTLST, which applies globally, can be found in the JobPak control file. To override the global configuration, use the EXCPTLST :FILE command as described in the “Job-processing options” section of Chapter 3, “The CONFIGIX Program.”



put the pdf of the report herer



pdf of report



pdf of report


Index

A

Accesslogs 55reports 75, 79security levels 22, 34

Action Control Sheet 110documenting errors 110format 110sample listing 112

Addressesreceiving messages 21sending messages 20, 21specifying 24

Archived jobs 8, 71restoring 60

B

Backup configuration file 123Banner page 8, 17Bypass

processing of $STDLISTSs 30

C

Column freeze, reports 86Comment lines 108

CONFIGIX program 10, 11Configuration file 13, 121

access 10CONFIGIX.JPAK.NSD 12global configuration 15job-specific configuration 25menus 12

configuration report 124Console messages 20

disable 21CONTINUE logic, on/off 31Copy

STDCOPY listing 17, 129to output file 50

CPU time 71

D

Defer printing 107Define

MPE commands 31, 109Deleting spoolfiles 30, 40Display

$STDLIST information 64, 79length, screen configuration 74

Do at Startup 25Documentation of errors 110


E

Email addresssender 24

EOJs, checking 17, 31Error checking 15, 18

controlling 109resume 17suspend 17

Error detection 18, 30, 109customizing 27detection suspension 31error text strings 27IF/THEN/ELSE logic 17, 30Missing error strings 26Non-error string texts 26

Error messages 7, 8, 17, 21, 31AutoDial 120disable 21receiving 21sending 21

Errors, documentation of 110Exceptions List 110, 130

record of errors 110report sample 130substitution values 111variable names 111

F

Finding text 52Folders

displaying 75finding 76

FormatAction Control Sheet 110STDLOG report 101

G

Global commands 13

H

Heading freeze, reports 86Help

technical support 6with STATUS 53

History, messages 8HPDeskManager ID 24

I

IBM job listings 64, 102Index pages, STDLOG report 42, 43, 102

Indexing reports 27, 34, 89Installation, JobRescue 10

J

Job stats 71JOBPAK.JPAK.NSD file 10Jobs

listing 54, 64, 79Job-specific commands 13, 14, 32

L

Line modeCommand reference 48parameters 46

Lines, listing 54, 84Logon ID 21, 26, 34, 39Logs 55

accessing logs 55creating STDLOG reports 40date and time of 68, 81finding a job in 66, 82scheduling retention management 40

M

Machine name 24Merge

$STDLISTs 41scheduling retention management 101

MERGE.PUB file 103Message output 20

configuration 16, 20disable 21displaying 57global 20receiving 21sending 21

Messages, history of 8, 57Missing error text strings 27Modem selection 119MPE commands

CONTINUE logic 17IF logic 30IF/THEN/ELSE logic 17, 30TELL command 31XEQ scripts

contents of 109disable global execution 31Do at Statup 25execute 22, 32job-specific execution 31

MPE commands (JPAKCOM) 93


N

Non-error text strings 27

O

OPACTION.PUB.NSD 110Output priority

printing deferral 107

P

Paging environment 115Parameters, Line mode (STATUS) 46PARMLINE.JPAK file 109Passwords 11Pattern matching 34, 35, 89PHONE file 115

dialing sequence 116job identification 116record format 116

Printby page 87, 88deferral 107device 30spoolfiles 16STDLOG report 103to MPE file 88

Print width 74Purge 19

$STDLISTs 20

R

READY state 108Reflection environement 89Reflection environment 78, 79, 87Report mode 75

access 75line navigation 83viewing configuration 77, 87

Reportingarchival 8changing defaults 105STDLOG 41, 101

Reportsaccess 39, 79changing screen configurations 78column freeze 84, 86deleting 38heading freeze 86indexing 34, 35, 89locating 80print by page 87

viewing generations 82Resuming JobRescue 93Retention management

$STDLIST access 55date & time of logs 41deleted files 13, 40displaying logs 40, 64scheduling 40

Retrieve archived files 60

S

Saving configurations 14Scheduling STDLOG reports 101Screen configuration 77Search

for character strings 61, 62for jobs 64, 80in the STDLOG report 41, 101

Securitymodifying access 33passwords 11

SHOWFOLDER command 48, 67Size, $STDLISTs 17Sort sequences, indexing 42, 43Spoolfile priorities 19, 107Spoolfiles

delay examination 108deletion of 30, 40empty 17foreign 16report versions 29, 82resume examination 93save options 29suspend examination 100

spoolfiles 30STATS listing 71STATUS

command reference 48Line mode parameters 46Report mode 75starting 75stopping 75version number 73

STDLISTsaccess to 79archived 9bypassing 30comment lines 108controlling examination phase 109copy to MPE file 31defer printing 107delay examination 108


deletion of files 30, 40displaying information 64EOJs 17, 31error checking 15, 18, 109examined 64finding jobs 66foreign 16IBM job listings 64, 102listing lines 54, 84maximum line number 17merge 41MPE commands 22open 72output priority 16, 17printing 129purging 19reporting 42, 43restoring archivals 60security 22STDCOPY listing 17, 129viewing 75

STDLOG reportconfiguration 41, 101creation of 41deletion of files 101error text strings 27format 101IBM job listings 64, 102index of jobs 102missing text strings 102non-error text strings 27printing 103retention management 40sample report 125searching for text 41, 101user-defined indexes 41, 42, 102versions 103

STOP command 93, 99SUSPEND command 100Suspend examination 100System identification 16, 23

T

Technical support 6TELL command 21, 31TELLUSER.JPAK file 21Text examination, control of 109Text strings

exceptions 27, 64find 52, 61, 62missing 26, 64

U

UNLOAD program 121

V

Variable name usage, OPACTION file 111Variables, Line mode (STATUS) 46Version number, STATUS 73Viewer 75

screen configuration 77

W

Width, maximum display length 74, 78


Documents

JobRescue™ Administrator’s Reference GuideChapter 1 Using JobRescue Nobix JobRescue Administrator’s Reference Guide 8 JobRescue can also verify that certain messages actually