jobresue reference guide - nobix › software › jrguide.pdfnobix, inc. shall not be liable for...

JobRescue™ reference guideversion 6.1

JobRescue™ reference guide

version 6.1November, 1998

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 notlimited 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 consequentialdamages in connection with the furnishing, performance or use of this material.

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

Copyright 1990, 1991, 1993, 1996, 1997, 1998 by Nobix, Inc., 6602 Owens Drive, SuiteOne Hundred, Pleasanton, CA 94588, Phone 800.538.3818, or 925.227.5600, Fax925.225.1420.

HP3000 and MPE/iX are trademarks, registered trademarks, trade names, and/or productsof Hewlett-Packard Company. JobRescue and ElectroPage are trademarks of Nobix, Inc. Allother trademarks are the property of their respective holders.

Nobix JobRescue reference guide 33

Table of contents

Preface .................................................................................................................................. 6JobPak and installation ...................................................................................................... 7How this document is organized......................................................................................... 7Assumptions ..................................................................................................................... 8Related documents ............................................................................................................ 8Technical support ............................................................................................................. 8

Chapter 1 .............................................................................................................................. 9

Using JobRescue.................................................................................................................... 9Introduction..................................................................................................................... 9Error detection ................................................................................................................. 9Error handling .................................................................................................................10Reporting and archiving....................................................................................................10

Report viewing...........................................................................................................11

Chapter 2 ............................................................................................................................ 12

Getting started .................................................................................................................... 12Startup............................................................................................................................12Running JobRescue ..........................................................................................................12

The CONFIGIX program ...........................................................................................13The STATUS program ...............................................................................................13Passwords and security ................................................................................................13

Stopping JobRescue..........................................................................................................13

Chapter 3 ............................................................................................................................ 14

The CONFIGIX program .................................................................................................... 14Introduction....................................................................................................................14Configuration menu .........................................................................................................15Saving configurations .......................................................................................................16Configuring global values..................................................................................................17

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

Configuring job-specific values ..........................................................................................26Customizing error detection ........................................................................................27$STDLIST save options ..............................................................................................28Job-processing options ................................................................................................30Executing specific :XEQ files .......................................................................................31E-mail distribution .....................................................................................................32Modifying file access...................................................................................................32


View access ................................................................................................................................33Pattern indexing .........................................................................................................................33

Configuring folder organization ...................................................................................35Adding folders ...........................................................................................................36Deleting folders..........................................................................................................36Adding reports to folders.............................................................................................37

Configuring report access............................................................................................................38

Configuring retention management..............................................................................38Configuring reporting.................................................................................................39

Sort options ...............................................................................................................................41Index string definitions ...............................................................................................................42

Chapter 4 ............................................................................................................................ 43

The STATUS program......................................................................................................... 43Line mode .......................................................................................................................43

Line mode conventions ...............................................................................................44Command reference .........................................................................................................46Report mode ...................................................................................................................73

Viewer—folder tree ....................................................................................................73Updating folder tree ...................................................................................................................74Viewer configuration options ......................................................................................................75

Report viewing...........................................................................................................76Locating reports .........................................................................................................................77Viewing report generations..........................................................................................................78

Report navigation.......................................................................................................79Line page controls ......................................................................................................................79String search ..............................................................................................................................80Heading and column freeze F5 ....................................................................................................81Miscellaneous keys F6.................................................................................................................83

Chapter 5 ............................................................................................................................ 88

The JPAKCOM program ..................................................................................................... 88Running JPAKCOM ........................................................................................................88JPAKCOM Commands ....................................................................................................89

Chapter 6 ............................................................................................................................ 97

The STDLOG report ........................................................................................................... 97STDLOG configuration ...................................................................................................97

Section I....................................................................................................................98Section II ..................................................................................................................98Section III .................................................................................................................99

Printing specific accounts..................................................................................................99Producing microfiche reports.....................................................................................100Changing reporting defaults ......................................................................................102

Chapter 7 ...........................................................................................................................103

Deferring $STDLISTs ........................................................................................................103

Chapter 8 ...........................................................................................................................104

Advanced Features ..............................................................................................................104Delay $STDLIST examination ........................................................................................104Special :COMMENT lines..............................................................................................104

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


Action control sheet .......................................................................................................106Substitution values ...................................................................................................107Additional alterations ...............................................................................................107

Sample action control sheet....................................................................................................... 108

Appendix A ........................................................................................................................109

The AutoDial program .......................................................................................................109Pager networks...............................................................................................................110Using AutoDial..............................................................................................................110

System setup............................................................................................................110PHONE file ..................................................................................................................110

PHONE record format .............................................................................................111Job identification...................................................................................................................... 111Dialing sequence ...................................................................................................................... 111Control characters in the dialing sequence.................................................................................. 111How the dialing sequence is sent ...............................................................................................112

Enabling AutoDial ...................................................................................................113Selecting a modem.................................................................................................................... 114

AutoDial in test mode...............................................................................................114Error messages ...............................................................................................................115

Appendix B ........................................................................................................................116

The UNLOAD program......................................................................................................116Create an ASCII configuration file .............................................................................116Edit the ASCII configuration file ...............................................................................117

Rules for editing the ASCII file.................................................................................................. 117

Backup the current configuration and load the edited ASCII file ...................................118Restore the backup configuration ...............................................................................118Print a configuration report .......................................................................................118

Appendix C ........................................................................................................................120

Standard log reports ...........................................................................................................120STDCOPY listing ..........................................................................................................124

Appendix D........................................................................................................................125

Exception list reports..........................................................................................................125

Index .................................................................................................................................129


Preface

This document provides operation, administration and configuration guidelines for theJobRescue software product from Nobix, Inc.

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

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

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

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

When used in conjunction with the Nobix JobTime product, JobRescue integrates errordetection with scheduling to ensure that no job is considered finished before it is thoroughlyexamined.


JobPak and installation

JobRescue is one of the three Nobix data center productivity tools bundled under the nameJobPak. The JobPak tools consist of the following:

• JobTime

• JobRescue™

• ElectroPage™

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

Although the JobPak products can be licensed and used individually, they all run in thebackground under the JobPak batch job. The installation of JobRescue, and/or any of theother JobPak products, is described in the JobPak Installation and Update Guide. Pleasereview this document before attempting to install or update JobRescue or any of the otherJobPak software tools.

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

How this document is organized

Chapter 1 Using JobRescue, provides an overview of the JobRescue product, basicdescriptions of its main features, and instructions for contacting Nobix Technical Support.

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 thebasic JobRescue configuration without stopping the program.

Chapter 4 The STATUS program, provides detailed information on how to run and usethe JobRescue STATUS program.

Chapter 5 The JPAKCOM program, provides detailed information on how to run and usethe JPAKCOM program.

Chapter 6 The STDLOG report, describes what a STDLOG is and how STDLOGs areused 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 AutoDial program, provides information on running and using the AutoDialprogram.

Appendix B Standard log reports, provides a sample STDLOG report.

Appendix C Exception list reports, provides a sample EXCPTLST report.


Assumptions

This document assumes that the reader is familiar with HP3000 computer systems and theMPE operating system. It is intended to be used by system administrators, managers and anyother users of the JobRescue software utility.

Readers should also be familiar with the HP3000 manuals published by the Hewlett-PackardCompany.

Related documents

• JobPak Installation and Update Guide

• JobTime Reference Guide

• ElectroPage Reference Guide

• JobPak Release Notes

• Nobix web site www.nobix.com

Technical support

The ElectroPage software uses the latest operating system technology and requires MPE/iX5.0 or later.

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

Nobix, Inc.6602 Owens DriveSuite One HundredPleasanton, CA 94588925.227.5600800.538.3818FAX 925.225.1420E-mail [email protected]

If you fax your question, include your name, return phone number, and fax number on thecover 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 aspractical.

Most problems and questions relate to the NSD account. To address these, we requireinformation about the NSD account structure and the files in the account. Please be signedon into the NSD account when you call us. This will expedite the solution.

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

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


Chapter 1

Using JobRescue

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

Introduction

JobRescue is an HP3000 software utility used in computer operations and systemmanagement.

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 listingsfrom any terminal or PC, local or remote, at any time.

Error detection

JobRescue 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 toaccommodate site specific requirements. Messages can apply to all jobs (global values), or bedesignated to apply to specific jobs (job specific values). In addition, global error messagescan be deactivated for specific jobs. Complete flexibility is provided to handle any situationthat might occur.

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

Chapter 1 Using JobRescue


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

Error handling

When JobRescue finds an error or other job exception within a $STDLIST, the programnotifies the operator and other users in two ways:

1 It sends messages to the system console indicating the job in question, and theinformation that an exception exists. These messages can then be sent to other onlineusers. 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 theerror are flagged above and below with a row of asterisks.

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

When an Exceptions List is read, the job name and the cause of the problem can be readilyidentified. Appendix C, 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 beconfigured 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 messageto a pager to notify someone of an error. For details, refer to Appendix A, The AutoDialprogram.

JobRescue logs all its console messages to a message history file. This file can be accessedthrough the STATUS program, as described in Chapter 4, The STATUS program. Themessage history file stores a preset number of messages and can be searched forward orbackward. JobRescue can also be configured to perform a specific action if a job is examinedand no errors are found. For instance, the program can be configured to execute certainMPE commands to continue processing.

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

Reporting and archiving

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

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

Chapter 1 Using JobRescue


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

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

Report viewing

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

The STATUS program can display a one-line summary of each job examined, showing jobnumber, 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 20000410 0918 1015 3073

13935 J5766 JOBPAK MGR.T61 270 19980729 1219 1235 3167

With only a few keystrokes, the STATUS program can be used to search for text inindividual or groups of online $STDLISTs. Using editor-like commands (Line mode) or amenu-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 allowssecurity access to be set at the user, account and operator capability levels. By default, anyuser 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 immediateuse. 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 forthe HP3000.

Startup

Nobix supplies a job control file named JOBPAK.JPAK.NSD that starts JobRescue. If you havealso licensed JobTime 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 JobRescue

JobRescue runs in the background under the JobPak batch job. If JobRescue is inadvertentlyterminated, just stream the job again. JobRescue should pick up where it left off without lossof data.

Chapter 2 Getting started


The CONFIGIX program

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

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

HELLO MGR.NSD

At the MPE prompt, type:

CONFIGIX.JPAK

CONFIGIX uses a forms-based menu interface to issue commands. Most of the commandsare self-explanatory and easy to understand. For detailed descriptions of configurationcommands, refer to Chapter 3, The CONFIGIX program.

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

The STATUS programAll viewing and searching of saved spoolfiles, $STDLISTs and reports is done using theSTATUS 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. Fordetails, refer to Chapter 4, The STATUS program.

Passwords and security

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

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

Stopping JobRescue

To 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 JobTime are licensed for use, they will also log off.

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


Chapter 3

The CONFIGIX program

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

Introduction

JobRescue provides the menu-driven program CONFIGIX to configure the software. Thefully qualified program name is CONFIGIX.JPAK.NSD.

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

JobRescue's basic configuration can be modified by making changes with the CONFIGIXprogram 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. Otherusers remain in a read-only status.

Chapter 3 The CONFIGIX program


Configuration menu

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

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

The Main Configuration menu contains the following menu items:

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

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

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

• Configure RETENTION Management—configuration time check, determining which filesneed 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 pathto another menu.) After a command is selected, a forms-based interface is displayed thatprompts 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 Configuringglobal values and Configuring job-specific values in this chapter.

Saving configurations

After configuring spoolfiles, or making changes to the configuration, press F8–PREV SCREENto 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 tothe Main Configuration menu.

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



Configuring global values

To configure global values, from the Main Configuration menu, select Configure GLOBALValues. 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 anerror 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 eachitem follow.



Processing options

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

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

• Allow foreign spoolfiles—enter a Y here to have the current system recognize $STDLISTsfrom jobs on other systems or from a previous run (owned by jobs that have anapostrophe 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 fieldto set the minimum output priority to which a $STDLIST can be queued and still beconsidered for examination by JobRescue.

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

• Maximum number of $STDLIST lines to process—enter the maximum number of lines in aspoolfile 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 detectingerrors in unexecuted portions of $STDLISTs.

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

• Check for :EOJ in every $STDLIST—enter a Y in this field to specify that any $STDLISTwithout 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 thoughsome error occurred.

For more information, refer to Job-processing options in this chapter.

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

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

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

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

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 isintended for use with ElectroPage.

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

For an example of an Exceptions List report with a banner, refer to Appendix C,Exception list reports.

• Suppress banner on STDCOPY—enter a Y to disable a banner page from automaticallybeing 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 optionsconfiguration. 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 ConfigureGlobal Values menu, select Global error string text. The Global Error String Text dialog boxappears:

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

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

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

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

• The entire text line to be searched for does not need to be defined; the phrase only needsto contain a portion of the text. For instance, the phrase “JOB FLUSHED” will actuallycapture the error string “REMAINDER OF JOB FLUSHED.” Character spacing and case areirrelevant, 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–EXITPROGRAM and respond to the Save prompt.

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


Nobix

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

JobRescue reference guide 2121

Post-processing options can be used to keep files online a certain amount of time after theyhave been examined, to purge (or not purge) $STDLISTs after examination, and to set theprinting priority to which non-$STDLIST spoolfiles will be adjusted after JobRescueexamines 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 and9999. This number instructs JobRescue to keep $STDLISTs online for the indicatednumber 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 tofill up with $STDLISTs, beginning with the date JobRescue was installed. Forconfiguration information on deleting saved spoolfiles, refer to Configuring retentionmanagement 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, anddeletes it from the spool system. The configuration can be set to purge globally byentering Y, and specifying certain files not to be purged. For details, refer to $STDLISTsave options in this chapter.

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



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

When there are existing uncompressed spoolfiles,

− Y causes JobRescue to compress those previously uncompressed spoolfiles during idleperiods.

− N does not cause JobRescue to uncompress existing compressed spoolfiles. Theyremain compressed. To uncompress these files, manually run the decompressionprogram against each compressed file.

Messaging configuration

After JobRescue has examined a $STDLIST, it sends a message to the system console, andother users, indicating the name of the job examined.

To control the message output to the console or to users, from the Configure Global Valuesmenu, 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 sendingmessages indicating the name of the job examined.

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

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

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

Any user whose logon user ID and account matches that of an examined $STDLIST isnotified 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 theconsole, add a list of these user names to the MPE file TELLUSER.JPAK. This file uses thesame syntax as the MPE TELL command. The names should consist of the logon ID in theform 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 scriptsTo globally execute a set of MPE commands after a $STDLIST or other spoolfile has beenexamined, 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 availablefor read access to the MGR.NSD user. For more information, refer to Chapter 8, AdvancedFeatures, Contents of MPE :XEQ scripts.

The MPE commands are performed by JobRescue in the NSD account. JobRescue alwaysexecutes the MPE commands after examining $STDLISTs and other spoolfiles. Files areexecuted in the order they appear, globally and then locally. See also Executing specific:XEQ files 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 ofthe computer system. Security is controlled through the use of the STATUS program.

To assign security restrictions to saved $STDLISTs and spoolfiles, from the ConfigureGlobal 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 standardsecurity 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 intheir account.

3—Check Access—users have no access unless specifically allowed. For details, refer toModifying file access in this chapter.



Miscellaneous system values

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

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 onthe Action Control Sheet. For multiple computer systems, give each system a differentdesignation; this can assist in identifying which report belongs with each system. Formore information, refer to Chapter 6, The STDLOG report and Chapter 8, AdvancedFeatures.

• Internet Mail ID—assigns a name to the JobPak software to use as the sender address fore-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 incorrector unavailable.

• 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 atsign (@), 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 tomail 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 timeJobRescue starts up.


Nobix

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

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

Configuring job-specific values

This section describes how to fine-tune the configuration to search for specific messages andto perform particular operations in certain jobs.

To configure job specific values, from the Main Configuration menu, select Configure JOBSpecific 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 thefields, 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 ormissing, they default to the wildcard character “@”. For instance, if you specify only theUser 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 jobsusing 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 thelist.

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. TheConfiguration 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 theyhave been examined

• Job processing options—configures values that modify the logic used to determine how ajob 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 detectionJobRescue searches for global error string text in all files. In addition, individual $STDLISTscan be searched for additional exceptions, specific to those $STDLISTs.


Nobix

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

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

• Non–error string text—enter a string of characters for JobRescue to find, but not to befound as an error. Use this to turn off certain broadly defined error strings with anarrowly 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 anon-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 anexception and an Exceptions List is printed. For an example of this list, refer toAppendix B, Standard log reports.

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

$ST


Press F1–Add Item and enter text in the corresponding field that appears at the bottom of theform. 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 serching for job-specific errors, JobRescue removes spaces and changes text toupper-case before the comparison.

DLIST save options

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



To modify the length of time a particular $STDLIST is kept online, from the ModifyConfiguration menu, select $STDLIST Save options. The $STDLIST Save Options dialogbox 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 willkeep 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 usethe 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 manygenerations (versions) of a job to be kept.

This field may be used in conjunction with the previous field. For instance, specify threegenerations 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 isdisabled.


Nobix

Job-processing options

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


The items listed correspond to the options described in Processing options in this chapter.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 Globalsettings specified for these same options.

• Delete spoolfile after processing—entering a Y in this field causes the GMLHJA and <=NA;=fields to have no effect (see the next two items below). The $STDLIST is deleted fromthe spool system.

• Set to this OUTPRI after processing—enter a value from 1 to 14. Entering a -1 in this fieldensures 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 torecognize 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 “RESUMEEXECUTION OF COMMANDS” is found, error checking resumes. The primary use of thiscommand is to prevent JobRescue from detecting errors caused by the MPE :TELLcommand 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 jobdid not contain an :EOJ; because the job never completed; or, because the job wasexecuting 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 whereanticipated errors may occur. Examination for phrases picks up again when the secondcolon (:) following the :CONTINUE is encountered. JobRescue ignores any error messagesor 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 commandfiles.

• 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 ofthe $STDLIST should be sent, if found with some type of exception. The job is thenprinted to this file command. The default file command for EXCPTLST is in theJobPak.JPAK JCL file.

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

Executing specific :XEQ files

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


Nobix

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

If both global and job-specific MPE commands are configured, JobRescue always executesthe global execution files first. Refer to MPE :XEQ scripts in this chapter.

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

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

Mod


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 thecomplete 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 toindicate sending as a non-error condition.

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

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

Use the following format for internet mail:

[email protected]

ifying file access

File access is controlled at the global level by the security level configuration. If the globalsecurity level is set to check access, it is necessary to grant access to certain users. For detailson global access setup, refer to Security level in this chapter. In addition, it is possible to


Nobix

extend additional access privileges to a user for a particular $STDLIST or spoolfile. Prior tomodifying 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 bemodified 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 thescreen, 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 (@), thepound sign (#), and the question mark (?).

Pattern indexing

Pattern indexing uses MPE pattern matching expressions to provide a means of delineatingindex values. In JobRescue, the pattern definition is treated as the index value.

Pattern matching expressions provide an extremely powerful yet flexible language for patternindexing. This provides maximum versatility in using virtually any character sequence orpattern to denote index entries, using MPE pattern matching characters and any literalcharacters, within a column or row range, as detailed below.


Nobix

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


Press F1–Add Item to enter a new pattern index. Nine entry fields appear at the bottom of thescreen, corresponding to the six parameters described below (the pages, rows and columnsentries each have a beginning and ending field). The numbers entered here must be relativeto 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 andsecond fields, respectively.

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

• Cols—enter the beginning column number and the ending column number in the fifthand 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 anysingle digit; the question mark (?) matches any single character. All other characterscorrespond 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 entryis completed in the other fields, a dash is automatically added as a separator between onenumber and another, as in 0–999.

To reconfigure existing index values already assigned to a saved spoolfile, refer to theREINDEX 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,


Nobix

Configuring folder organizationJobRescue can be configured to create an on-line folder tree to store $STDLISTs insidefolders. The STATUS program can then be used to view the $STDLISTs (described inChapter 4, The STATUS program).

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


The JOBPAK FOLDER acts as an anchor for the folder organizational system. Like a filecabinet, 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 aleading period. Each subsequent level is indented by an additional leading period. Forinstance, one leading period is equivalent to the first level down from the top level; twoleading 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 arevisible on the screen at one time. Folders within each level are sorted alphabetically andnumerically.

In the example above:

• There are four visible top-level folders: ALL-REPORTS, M.I.S REPORTS,MANUFACTURING, and SALES.

• In the MANUFACTURING folder, there are two first-level folders: CUSTOMERMASTER and PRODUCT MASTER.

• In the SALES folder, there are two first-level folders: SALES ORDER and SALES REPS.

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

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


Nobix

Adding foldersTo add folders to a folder tree:

1 Position the cursor on the folder within which the new folder is to be added (it is notnecessary to position the cursor on the JobPak folder when adding top-level folders). Usethe 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 theToplvl field to create a top-level folder. Enter an N to add lower-level folders. Lower-levelfolders are the default if this field is left empty.

Dele


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

4 To save the configuration, press >0 until the Save/Exit screen prompt appears. Tab toOKAY and press ENTER before exiting.

ting foldersTo delete a folder:

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

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


Nobix

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–AddReport. 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 Chapter 4, The STATUSprogram, Report mode.

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


Nobix

Configuring report access

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

Con


The selected folder is listed at the top of the form. Press F1–ADD ITEM to assign access to aparticular user. Three fields appear at the bottom of the screen. Enter the user's logon ID asfollows:

• 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 beused with three types of pattern matching: the at sign (@), the pound sign (#), and thequestion mark (?).

If a view access list is not specified for a folder, view access is determined by the globalsecurity 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 folderswithin it.

figuring 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 timethe Retention Management cycle runs, a new set of $STDLISTs becomes available as thecurrent set, or Log 0. The 0 applies to $STDLISTs that have not yet been through aRetention Management cycle.

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


Nobix

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

Con


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) ofthe week marked with an X.

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

• The MPE command file MERGE.PUB is executed.

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

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

• A new log is created, and the log information is updated to show Log 1 as being theperiod of time from the most previous Log 1 to the current date and time. The previousLog 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 theSHOWDELETELOG command in STATUS.

figuring reportingA STDLOG report contains information about the most recently examined $STDLISTs. ASTDLOG 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. Indexeshelp locate text in Section III quickly, which is increasingly important as batch activityincreases.

Appendix C contains a sample STDLOG report. For detailed information about the fieldand indicators in a STDLOG report, refer to Chapter 6, The STDLOG report.

To configure a STDLOG report, from the Main Configuration menu, select ConfigureSTDLOG 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 sortsequences or options. Reports contain job indexes in Section I; these indexes are the keyto the body of the report, which contains the text of the $STDLISTs. For moreinformation, refer to Sort options in this chapter.

• Index String Definitions—enables the creation of indexes in the STDLOG report. SectionII lists user-defined indexes. For more information, refer to Index string definitions inthis chapter.


Nobix

Sort options

To modify sort sequences or options, from the Configure STDLOG Report menu, selectSort 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 jobindex 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 thejob 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 namesequence, 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 StringDefinitions. The Index String Definitions dialog box appears:

The text strings entered in this configuration will be used to create index pages in theSTDLOG report. Any text found in a $STDLIST can be indexed with the appropriatephrase 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 20characters, 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 notprint that index page.

For a detailed explanation of each section of the STDLOG report, refer to Chapter 6 TheSTDLOG report.


Chapter 4

The STATUS program

The STATUS program allows users to interactively view and search saved spoolfiles. AfterJobRescue has examined and saved a spoolfile, the $STDLIST will be available online via theSTATUS program. The saved $STDLISTs can be accessed using command line entry inLine 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 mode

To 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 withspecific parameters, as detailed below.

Chapter 4 The STATUS program


Line mode conventionsThe parameters described below are used in certain Line mode commands described in thischapter.

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

Parameters Descriptions

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

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

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

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

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

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

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

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

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

SHOW [USER.]ACCOUNT ; OK,EX

[BACKWARD] An optional keyword that informs JobRescue to print the display on alast-in, first-out basis (LIFO). In other words, the most recent JobRescuemessages 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 $STDLISTand is not found.

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

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

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



Parameters Descriptions

<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 beaccessed. 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 toprevious sets. Each time $STDLISTs are placed on the STDLOG report,a new set of $STDLISTs become available as the current set. For moreinformation, refer to Chapter 3, The CONFIGIX program, Configuringretention management.

The number 0 applies to $STDLISTs that have not been placed into aSTDLOG report; 1 is the most recent log; 2 is the set just before 1; 3 isthe 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 carriagecontrol. If this file is to be a disc file, specify “DEV=DISC” on areferenced :FILE command.

In the following keywords, only one of any arguments that are separatedby the pipe character (|) 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 followingindicators:

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 arange. They must be separated by the slash (/). A plus (+) or minus (-)displacement value can also be entered.

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



The job name uses standard MPE formatting, as in UPDATE,MGR.FINANCE. If anyportions 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 accountname portion; JobRescue assumes that the session and user names are “@”. If the user nameand account are specified, JobRescue assumes that the job name is “@”. If job-name isomitted, @,@.@ is used.

Command reference

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

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.

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(*).

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



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 toan output file.

Use the TEXT command to open a file first, before using this command. The TEXT file mightbe 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 awarethat 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

Funct ion

Closes the STATUS program.

Syntax

EXIT

Operation

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

If you type =PAL from the 6f6 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 toupper-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

Funct ion

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. TypeEXIT to return to the STATUS prompt (>>).

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

Example

>>HELP>>HELP SHOWALL

See also

EXIT



LIST

Funct ion

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 TEXTcommand). 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 anexception. This format applies only to $STDLISTs.

Specifying EXCEPTIONS tells JobRescue that to view only lines within the text that JobRescueconsiders to have caused the exception or error, or lines with text searched for that could notbe 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 RetentionManagement cycle (refer to Chapter 3, The CONFIGIX program). Use the LOG commandto move from one day’s set of $STDLISTs to another.

$STDLISTs are saved in JobRescue for as long as their configuration dictates. The numberof days $STDLISTs are kept is entered at the Post Processing Options dialog box. (refer toChapter 3, The CONFIGIX program).

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

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

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

Note: If other $STDLISTs than those available at LOG 0 are examined, the commandprompt 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 1998/07/29 10:20:27 –> present.>>log 3Log is 3, from 1998/07/23 00:00:23 –> 1998/07/24 00:00:28.>3>showlog

There are 28 logs available.

Log# From Date/Time To Date/Time

0 WED, 1998/07/29 10:20:27 –> present 1 TUE, 1998/07/28 00:00:16 –> WED, 1998/07/29 10:20:27 2 FRI, 1998/07/24 00:00:28 –> TUE, 1998/07/28 00:00:16 3 *THU, 1998/07/23 00:00:23 –> FRI, 1998/07/24 00:00:28 4 WED, 1998/07/22 10:20:06 –> THU, 1998/07/23 00:00:23 5 TUE, 1998/07/21 00:00:23 –> WED, 1998/07/22 10:20:06 6 FRI, 1998/07/17 00:00:26 –> TUE, 1998/07/21 00:00:23 7 THU, 1998/07/16 00:00:25 –> FRI, 1998/07/17 00:00:26 8 WED, 1998/07/15 10:20:06 –> THU, 1998/07/16 00:00:25 9 TUE, 1998/07/14 00:00:25 –> WED, 1998/07/15 10:20:06 10 FRI, 1998/07/10 00:00:24 –> TUE, 1998/07/14 00:00:25 11 THU, 1998/07/09 00:00:24 –> FRI, 1998/07/10 00:00:24 12 WED, 1998/07/08 10:20:06 –> THU, 1998/07/09 00:00:24



See also

EXIT, SEARCH, SHOW, SHOWLOG

Configuration file commands: Configure RETENTION Management, Post-processingoptions.



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 systemconsole on your terminal.

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

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

When the <phrase> parameter is used, JobRescue will only print messages containing amatching character string. If the MESSAGES command is used without parameters, messageswill 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—1998/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, SHOWLOG

Configure 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 commandentered and allows changes to be made to it. When editing is complete, press ENTER todisplay 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 Icommand 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 theedited 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 editedcommand.

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

Example

>> SHOUWUNKNOWN COMMAND

>> REDOSHOUW

D <Return>SHOW



Multiple changes—When ENTER is pressed once, STATUS displays the edited version of thecommand. After ENTER is pressed once to display the edited command, additional changescan 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 aspart of normal system backup procedures. Once a file has been deleted by the RetentionManagement cycle, the only way to bring that file back is to restore it from the systembackup media.

To determine which file to restore from the backup media, use the SHOWDELETELOGcommand, which displays the logon IDs of $STDLISTs, as well as the filenames they weresaved 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 restoredfile.

When an uncompressed file is restored based on information obtained fromSHOWDELETELOG, 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 theend of the base filename.

Compressed files encapsulate the header information inside the compressed file, andtherefore 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 havebeen restored into the NSD account before using the RETRIEVE command.

Example

Log is 0, from WED, JUL 26, 1998, 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 inany examined $STDLISTs, within the currently open log group, that match <job–name>. If ajob 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 thatpertain to a particular Log (see the LOG command).

The search begins with the most recently examined $STDLIST and continues to the oldestexamined $STDLIST, displaying in descending date/time sequence. JobRescue shifts all textto 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, 1998, 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 stringin any examined $STDLISTs, within all available log groups, that match <job–name>. If ajob 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 oldestexamined $STDLIST, displaying in descending date/time sequence. JobRescue shifts all textto 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, 1998, 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, 1998, 12:06 PM.

Log #25 file #1899, files1/A.14776.898019336, #J8621, $STDLIST:JOBPAK,MGR.T61 32481 CPU sec. = 18720. elapsed min. = 8676. TUE, JUN 16, 1998, 10:39 AM.

Log #28 file #59, files1/A.14746.897498220, #J8597, $STDLIST:JOBPAK,MGR.T61 519 CPU sec. = 402. elapsed min. = 35. WED, JUN 10, 1998, 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 isentered 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 octalvalue.

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 andIBM 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 beIBM 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 $STDLISTinformation.

The <#Jnnn> parameter, used in format (2) above, signals JobRescue to display only thoseentries 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) isused, JobRescue will display more detailed information about the file. Format (4) will showall $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 asemicolon. When <job–name> is specified, it must be the first parameter. If any otherparameters are also entered, <job–name> must be delimited by a semicolon (;). The otherparameters 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. Cpu 35 8495 JOBPAK MGR.T61 1556 20000410 0918 1015 307313935 J5766 JOBPAK MGR.T61 270 19980729 1219 1235 3167 2 $STDLIST(s) Displayed Total 2250 6240

Average 1125 3120>>SHOW @.T61; EX 0 $STDLIST(s) Displayed. Total 0 0

Average 0 0

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

See also

OPEN, RETRIEVE, SHOWALL, TEXT



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 (thecurrent day’s) and continuing through the last log available. This is a convenient way tosearch 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 otheroptional parameters.

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

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

Example

>> SHOWALL UPDATE,@.@

See also

LOG, SHOW

Configuration file commands: Configure RETENTION ManagementConfigure 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 samebranch structure. It displays the number of spoolfiles in each folder and the time the folderwas last updated with a new spoolfile.

The <folder-name> parameter is optional. Use the name of the folder in quotes. If folder-nameis 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 1998/09/04 09:54:20M.I.S. REPORTS 129 1998/09/04 03:27:53MANUFACTURING 538 1998/09/03 18:37:12SALES 68 1998/09/04 09:54:20

Example

>>SHOWFOLDER "SALES"

FolderName-------------* Count Latest-----------------*SALES 33 1998/09/04 09:54:20..SALES ORDER 35 1998/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 theoptional 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 processingoptions dialog in the CONFIGIX program. In addition, the Retention Management cycle musthave been configured. For details, refer to Chapter 3, The CONFIGIX program.

Example

>>SHOWLOGThere are 28 logs available.

Log# From Date/Time To Date/Time 0 WED, 1998/07/29 10:20:27 –> present 1 TUE, 1998/07/28 00:00:16 –> WED, 1998/07/29 10:20:27 2 FRI, 1998/07/24 00:00:28 –> TUE, 1998/07/28 00:00:16 3 THU, 1998/07/23 00:00:23 –> FRI, 1998/07/24 00:00:28 4 WED, 1998/07/22 10:20:06 –> THU, 1998/07/23 00:00:23 5 TUE, 1998/07/21 00:00:23 –> WED, 1998/07/22 10:20:06 6 FRI, 1998/07/17 00:00:26 –> TUE, 1998/07/21 00:00:23 7 THU, 1998/07/16 00:00:25 –> FRI, 1998/07/17 00:00:26 8 WED, 1998/07/15 10:20:06 –> THU, 1998/07/16 00:00:25 9 TUE, 1998/07/14 00:00:25 –> WED, 1998/07/15 10:20:06 10 FRI, 1998/07/10 00:00:24 –> TUE, 1998/07/14 00:00:25 11 THU, 1998/07/09 00:00:24 –> FRI, 1998/07/10 00:00:24 12 WED, 1998/07/08 10:20:06 –> THU, 1998/07/09 00:00:24 13 TUE, 1998/07/07 00:00:25 –> WED, 1998/07/08 10:20:06 14 FRI, 1998/07/03 00:00:21 –> TUE, 1998/07/07 00:00:25 15 THU, 1998/07/02 00:00:21 –> FRI, 1998/07/03 00:00:21 16 WED, 1998/07/01 10:20:05 –> THU, 1998/07/02 00:00:21 17 TUE, 1998/06/30 00:00:25 –> WED, 1998/07/01 10:20:05 18 FRI, 1998/06/26 00:00:19 –> TUE, 1998/06/30 00:00:25

See also

LOG

Configuration file command: Configure RETENTION ManagementConfigure Global Values command: Post–processing options.



SHOWDELETELOG

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

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 todetermine 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 tellsJobRescue 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.AccountSaved PurgedR.14783.897499216.cmp J8621 STDLOG JOBPAK MGR.T61 980610 001003R.15168.897548428.cmp J8621 STDLOG JOBPA MGR.T61 980611 001003R.17108.897980441.cmp J8621 STDLOG JOBPAK MGR.T61 980616 001003R.18073.898153244.cmp J10488 STDLOG JOBPAK MGR.T61 980618 001003R.20025.898585252.cmp J10488 STDLOG JOBPAK MGR.T61 980623 001003R.21433.898844434.cmp J10488 STDLOG JOBPAK MGR.T61 0626 001003R.22850.899190046.cmp J10488 STDLOG JOBPAK MGR.T61 980630 001003R.32895.904028436.cmp J5833 STDLOG JOBPAK MGR.T61 980825 001003R.32897.904201234.cmp J5833 STDLOG JOBPAK MGR.T61 980827 001003R.32902.904633226.cmp J5833 STDLOG JOBPAK MGR.T61 980901 001003R.32907.905361642.cmp J5833 STDLOG JOBPAK MGR.T61 980909 001003R.33398.905966424.cmp J5833 STDLOG JOBPAK MGR.T61 980916 001003R.33747.906015639.cmp J5833 STDLOG JOBPAK MGR.T61 980917 001003R.34207.906102032.cmp J5833 STDLOG JOBPAK MGR.T61 980918 001003R.35617.906447663.cmp J5833 STDLOG JOBPAK MGR.T61 980922 001003A.35889.907258951.cmp J6 $STDLIST JOBPAK MGR.T61 981001 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.>>



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 arecurrently being stored in JobRescue. These statistical averages are based upon data availablein 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 isused, it defaults to the account name portion; JobRescue assumes that the session and usernames are @. If the user name and account are specified, JobRescue assumes that the jobname is @.

Example

>>STATSDisplaying job set @,@.T61

Log# F# Job# Logon at Logoff at Elapsed Cpu Sec %Cpu #Lines Ex 0 184 J18 20001005 1936 20001005 2002 26 18 1 146 6 5 J7 19981001 0922 19981001 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 andaverage of each of the columns (for timing values and line numbers). All Logs are displayedwhen the STATS command is entered without a filename parameter.



TEXT

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

Syntax

TEXT <file–number>

TEXT <#Jnnn>

Operation

The TEXT command opens the saved $STDLIST file, corresponding to either the file numberor 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 theSHOW 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. Cpu 184 J18 JOBPAK MGR.T61 146 20001005 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 theSTATUS program.



WIDTH

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

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 forprint width.

WIDTH does not affect the COPY command.

Example

>> WIDTH 79>> W 67

See also

COPY, LIST


Nobix

Report mode

When Report mode is accessed in the STATUS program, $STDLISTs and individual reportscan be viewed using a user interface called the Viewer. Enter the STATUS program bytyping:

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 treeWhen the Viewer initially opens, the JobPak folder tree appears:


The folder tree contains a hierarchical listing of all of the folders containing the reportscurrently in the system. Refer to Chapter 3, The CONFIGIX program, Configuring folderorganization.

Function buttons appear at the bottom of the Viewer screens, providing a shortcut methodto execute commands. These buttons correspond to the >)È>0 function keys on thekeyboard. (Some of these buttons remain undefined.)

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


Nobix

To display just the top-level folders, select F4–COLLAPSE ALL. The total number of spoolfilesstored 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 andpress 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 theconfiguration that have not been recorded. To update the folder tree and create a current listof folders and reports, press F6–REFRESH DISPLAY.


Nobix

Viewer configuration options

In Report mode, the screen configuration can be changed for individual viewing. At theViewer folder tree screen, select F5–CHANGE CONFIG. The Screen Configuration Optionsdialog 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 scrollthrough the report when using the UP and DOWN arrow keys.

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

• Maximum scroll to right edge (#columns)—enter a number from 80 to 264 to change thedefined 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 donot change.

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

This feature automatically detects how many columns and rows the display has, and willthen 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 thesubfolders in the hierarchy.

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


Nobix

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

Report viewing

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

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


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


Nobix

Reports are sorted by File designation, Account name, User name, Job/Session, and timesequence (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 spoolfileoriginated.

Locating reports

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

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



Nobix

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 indescending time sequence, as in this example:

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

A tilde appearing next to an individual report listing indicates that page numbering withinthe report is approximate (no tilde indicates there is carriage control in those files), asexplained 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 reportindicating the beginning and ending of each new page. The example above shows a reportwithout carriage control; however, sometimes this type of report may also display an initialpage 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 linesrelative to one. Line number one, indicating the top line, changes while scrolling up ordown, 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 RIGHTand LEFT arrow keys, these column numbers will change. These parameters can bemanipulated using the configuration options detailed in this chapter.

Report navigationTo navigate within a report, use the Page Up and Page Down keys on the keyboard (a pagecorresponds to a full-screen view, as opposed to a complete document page), or use the UPand 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.

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.

Line page controls

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

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

F2–ShowLine Numbers—displays line numbers along the left-hand side of the page (offsets thetext 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 ispressed without entering a page number, the prompt disappears.

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


Nobix

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

F5 is undefined for the Line Page Controls.

String search

Press F3–String Search to find text in a report. The function button display toggles to thefollowing selections:

F1–Enter FindText—at the prompt enter text to be found. Enter f or b to search forward orbackward 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 boxappears:


Supply values in the fields as described below:

• Remove spaces during search—enter Y to remove spaces from a text string specified andthe 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 thespecified text string.

• Search frozen heading area—enter Y to search the locked lines at the top of the screen. Todefine 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 wherethe search begins.

• Right–most column to search—enter the number of the rightmost column to define wherethe 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 atthe top of the screen. To lock or freeze a heading or column in place, press F5–Head/ColFreeze. 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, andtoggles the function button display to the following:

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

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

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

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

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

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

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

F1–Add Segment Concatenates selected columns and automatically creates aseparate view of the selection, which can be viewed by exitingColumn Freeze. When this function is selected, the columnnumbers (read vertically, beginning with the numeral 10) areautomatically displayed at the bottom of the report, as shownbelow:

At the prompt, enter a beginning column number and adelimiter (space or comma) and an ending column number. Thedelineated columns are highlighted when ENTER is pressed. ExitColumn 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 todeactivate.

F3 Remove LastSegment

Removes highlighted columns from the report display that wasadded with Add Segment.

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

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


Nobix

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 thefollowing selections:

F1–Change Config—displays options for changing the report viewing configuration, asdescribed previously in Viewer configuration options.

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


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

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



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

Input for Print by Page is as follows:

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

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

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

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

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

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

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

• :FILE command for system spooler destination—in an HP3000 environment, enter theMPE :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 andending pages.



If using Reflection, before processing this configuration, activate the print bypass feature toprevent 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 PrintSetup command. Highlight or mark the Bypass Windows Print Driver option. Also, highlightor 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 configurationfor the current job.

F4–User Key—can be configured as a user-defined key; the button on the display will changeto 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 savedwith a Pattern indexing configuration, as detailed in Chapter 3, The CONFIGIX program,Configuring job-specific values.



When this function is selected, a list box is displayed that shows the word, line and columnentries 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. Theindex name, next to the index number, is assigned in the Description field of the PatternIndexing 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 andline in the report.

If a report has more than one configured index, press F1–Switch Index to toggle the display tothe 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 rangeand quickly accesses the specified range, as shown below using the example Index #3:

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

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 JPAKCOMcommand, REINDEX (refer to Chapter 5, The JPAKCOM program).


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. Forexample, 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 JPAKCOM

JPAKCOM 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 Nobix

WED, JUL 29, 1998, 3:16 PMJobPak:

Chapter 5 The JPAKCOM program


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 isterminated 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 acolon (:).

Operation

This command allows you to instruct JobRescue to execute the command from within itsrunning 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 devicethan 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 :MPEcommand.



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 byMPE 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 andJobRescue is not going to examine it. You must determine whether the spoolfile is okay toprint.

The PROCESS command can be used to process spoolfiles that have this disposition withJobRescue. 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 filesstored in the NSD account can be displayed using the FINFO option in the STATUSprogram’s SHOW command. This parameter is required.

Operation

Any previously generated index values are deleted and new index values are developed, basedon 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 orderlyway 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 anyspoolfile 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 RetentionManagement cycle produces a STDLOG report. The STDLOG report contains all jobslisted 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 $STDLISTsbecomes available as the current set. The current set of $STDLISTs is placed in theSTDLOG report at the next Retention Management cycle, as specified in the configurationprogram. Refer to Chapter 3, The CONFIGIX program, Configuring retentionmanagement.

STDLOG configuration

A 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 moreimportant as the level of batch activity increases.

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

For a sample STDLOG, refer to Appendix B, Standard log reports.

Chapter 6 The STDLOG report


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

Section IThe 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 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 examinedas follows:

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

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

For more information, refer to Chapter 3, The CONFIGIX program, Configuring job-specific values.

The sorting sequence of Section I is controlled by using the Sort Options command underConfigure STDLOG Report on the Main Configuration menu. The sorting sequence can beformatted by job account, number, or name as detailed in Chapter 3, The CONFIGIXprogram.

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

Section IIIndexes can be created in Section II using the Index string definitions command underConfiguring reporting on the Main Configuration menu, as detailed in Chapter 3, TheCONFIGIX program.

The heading of each index page in Section II contains the name of the index in the upperleft-hand corner. JobRescue picks up the word following the word or phrase indexed, andlists it as the Parameter, in the body of the index page. The page number or numbers where itappears in Section III, are displayed next to the Parameter word. (See the example inAppendix B, Standard log reports.)



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

The default configuration is supplied with index references for the :RUN and :FILEcommands. Refer to Chapter 3, The CONFIGIX program, Job-processing options.

Section IIIEach $STDLIST in Section III begins at the top of a new page, and every page contains apage 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; thisprevents unnecessary paper waste.

Printing specific accounts

The STDLOG report is produced when a file named MERGE.PUB is executed; this XEQ fileprints a single STDLOG report. The program STDLOGR. is run from this file to producethe report.

Typically, MERGE.PUB is run at the end of a configured retention management cycle (asdescribed 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=LP

STDLOGR.PUB –indexonly 1 @ @ @

If a printed copy of the STDLOG report is not required, comment out the STDLOGRcommand 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 parms

stdlogr.jpak.nsd;info=“!parms”

For different versions of a STDLOG report, you can add the applicable STDLOGR commandsto 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 SHOWLOGcommand 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 wouldenter 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 allappear as notext.

• –exonly specifies that all jobs appear in Section I, but the text appears in Section III foronly those $STDLISTS that have exceptions. Jobs that do not have exceptions appearwith 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 toredirect 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" andending 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 report

comment 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 stdlogcomment 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 true



while stayinloop input aline < readback setvar beginchars str(aline,1,5) if beginchars = "INPUT" then setvar stayinloop false elseif str(aline,1,2) = "#O" then setvar strdfid str(aline,3,7)

setvar testdfid !strdfid if testdfid > highest_dfid then setvar highest_dfid testdfid endif endifendwhileif !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 tothe 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 values 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 byJobRescue. To ensure that $STDLISTs do not print, they must be deferred before they areclosed by the system. JobRescue defers $STDLISTs automatically; this capability has beenincluded as part of the JobPak job control.

It is not necessary to manually defer $STDLISTs in JobRescue, since the programautomatically does this by setting a priority of zero when the spoolfile closes. Spoolfilesinitially exhibit whatever the priority was set to, the default priority being 8, and thenchange 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 thespoolfile, depending on the JobRescue configuration.

The JPEnable command syntax activates the deferral process, ensuring that JobRescue willcontinually 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 thequeue. These programs immediately examine new spoolfiles for processing. To delay whenJobRescue examines spoolfiles, place the DELAYEXAMSECS variable in the JOBPAK.JPAKfile.

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 lineJP02SXL.JPAK.

Special :COMMENT lines

JobRescue usually ignores any comment lines it finds in $STDLISTs. However, a specialcomment line can be entered in job control to control the actions of JobRescue. Thesespecial comments control the examination phase by instructing JobRescue to skip overcertain portions of the $STDLIST.

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

Chapter 8 Advanced features


Controlling text examinationWith comment line commands, JobRescue can be instructed not to check for errors incertain portions of the $STDLIST. This also means that JobRescue does not look for anytext defined as a Missing error string text entry in the configuration, as described in Chapter3, The CONFIGIX program, Customizing error detection.

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 theend of the file is reached.

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

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

Warning: Do not use these special comment lines if the job processing option, FollowMPE :IF commands in $STDLISTs, is also used. Refer to Chapter 3, The CONFIGIXprogram, Configuring job-specific values.

Contents of MPE :XEQ scripts

To facilitate parameter passing and substitution, a common PARM header line must be usedin 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 variablenames between multiple processes running in the same session. Be aware that once variableshave been assigned, they are not deleted at the conclusion of the :XEQ file being run, andthey 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 ascript have the dfid number of the spoolfile being processed incorporated into their name,thus making them unique. Also, the :DELETEVAR command should be executed referencingany names assigned during the operation of the script.

The required PARM header line is in a file named PARMLINE.JPAK and can be copied intoany :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.

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.

Action control sheet

The 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 ofjobs found to have an exception. This document can be filed, or it can be used for laterreference about a problem job.

The format of the ACS is stored in a file named OPACTION.PUB.NSD. JobRescue reads thisfile 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 132characters. 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 65lines of text will produce a two-page ACS. The first page will have 60 lines and the secondpage will only have five lines.

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



Substitution valuesVariable names can be entered in the OPACTION file. JobRescue will substitute workingvalues for these names. There are twenty-six variable names supported. The following listshows 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 #Jnnnn.

$DATELINE Current date and time, 27 characters.

$DATE Current date, format-21NOV98.

$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-21NOV98.

$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, #Onnnn.

$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 alterationsThe 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 tothe EXCPTLST spoolfile immediately in front of the OPACTION file. OPCTL can containcontrol characters that send commands to the printer. For instance, this file can be used tochange the character set, font type, or font rotation.



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

Since JobRescue writes OPCTL to EXCPTLST immediately after the $STDLIST text andimmediately before OPACTION, this file can be used creatively to design a useful ActionControl 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 takesplace.

$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 $NAME IS $XCOUNT. PROBLEM(S) FOUND WERE:

$XLINE01$XLINE02$XLINE03$XLINE04$XLINE05$XLINE06$XLINE07$XLINE08$XLINE09$XLINE10

********************PROBLEM SOLUTION ****************

PROBLEM TYPE: ___1–HARDWARE, 2–SYSTEM SOFTWARE, 3–OPERATIONS 4–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. AutoDialcan tell the modem (or other automatic calling unit) to dial a pager number to alertcomputer personnel that a particular job has an error. AutoDial can dial different numbersfor different jobs; this can be helpful when different people are responsible for these jobsand/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 performedwhen 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 bebuilt 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 theassociated phone numbers which should be called if there is an error. Wildcards may be usedto match job names.

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

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 appropriatecharacter sequence to this device. A coded numeric message can also be included that couldbe 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

Appendix A The AutoDial program


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

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

Pager networks

Since AutoDial is intended primarily for use in a pager network or environment, you shouldbe familiar with the equipment to be used. This applies not only to the modem equipment atthe 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-displaypagers, or with more sophisticated numeric display pagers. Make sure that the pager networkto be accessed is compatible with AutoDial.

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

Using AutoDial

There are many reasons why you might want JobRescue to contact a pager number when itdetects a job error. For example, using AutoDial can reduce the time that data processingpersonnel 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 JobPakproduct JobTime), it may even be possible to have an unmanned computer room. This canbe beneficial at night, or at other times when personnel are not available in the computerroom. Since AutoDial can call different numbers for different jobs, simply have AutoDialcontact the person responsible for a particular batch job or system and alert them to thepresence of a batch error.

System setupThere 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 fileand reference the appropriate logical device number and the filename.

AutoDial accesses a modem through the MPE file system by opening the logical device thatconnects the modem to the computer system; therefore, you must enter a :FILE command totell AutoDial the logical device number (LDN) of the modem that is to be used. Thefilename 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 file

The PHONE file PHONE.PUB.NSD is a cross-reference of job names and dialing sequences. Anysuitable text editor can be used to create this file. The PHONE file must be unnumbered andno 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 formatThe format of each record is free-form. The job ID must appear to the left of the firstsemicolon delimiter. The dialing sequence begins immediately after the first semicolon oneach record. Spaces in the first position after the semicolon become part of the dialingsequence. 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 afterthe 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 withthe first non-blank character on each record.

The job ID can be entered in upper- or lower-case. Only ASCII letters and numbers and theMPE 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, theydefault to the wildcard character “@”. For example, a job ID that matches all jobs would bespecified as:

@,@.@ ;

AutoDial selects the first PHONE record that matches. If a matching job ID has not beendefined 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. Thedialing sequence may contain any valid ASCII characters. Upper- and lower-case arepreserved in this portion of the PHONE record.

Caution: The complete dialing sequence must be on the same line as its corresponding jobID. 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 sometype of action. Control characters can be defined by placing a caret (^) in front of thecharacter. For example, if a carriage return is specified as a CTRL–M, this would berepresented as ^M. A CTRL–B would be defined as ^B. To define the actual caret characteritself, use two carets next to each other, as in ^^.



To instruct AutoDial to pause for a half-second, enter a dollar sign ($) into the dialingsequence. Dollar signs are not transmitted to the modem; therefore, they only causeAutoDial 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 percomma, 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 thepager.

• 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 anexample. Please check the modem manual to verify.

How the dialing sequence is sent

AutoDial sends the dialing sequence character by character, beginning with the firstcharacter 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 delayis used because some modems cannot handle a faster rate. AutoDial is trying to act like aperson typing through a terminal connected to the modem.

Note: AutoDial opens the modem logical device as a file. The line speed is not changedfrom the device’s MPE configured value. The modem port is set to the equivalent of termtype 18. The port is opened for read/write access.

The dialing sequence should contain not only everything required to connect the modem tothe pager network, but also the information that must be sent to the pager equipment. Inother words, the dialing sequence must contain the pager phone number and the number (ifany) to be displayed on the pager itself.

If the modem requires a confirming carriage return before it will dial a number, be sure toinclude an extra CTRL–M (^M) in the dialing sequence.

Pager networks usually require a certain amount of time to answer an incoming call from themodem. Some networks answer on or before the first ring, while others answer on the thirdor fourth ring. Time must be allowed for the network to answer before sending a numberthat is to be displayed on the pager. Most autodialing modems allow a pause or delaycharacter to be included in the dialing sequence. On some modems, the comma (,) or letterK 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 bedisplayed on the pager.

Note: Although most telephone networks allow pulse dialing, most display pager networksrequire tone dialing.

After the sequence is sent, AutoDial pauses for thirty seconds before it closes the logicaldevice 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 AUTODIAL COMMENT program. Modify the command line "setvar PORTLDN 21" COMMENT to the port you will use for your modem.

if !ExCnt = 0 and !MissingCnt = 0 then return endif

echo AUTODIAL.XEQ !JobPreFix!JobNo BEG !HPDATEF !HPTIMEF

setvar cnt!Dfid 0 setvar stayinloop!Dfid true while stayinloop!Dfid setjcw cierror 0 continue build autolock>$null if cierror = 0 then setvar stayinloop!Dfid false else pause 20 setvar cnt!Dfid cnt!Dfid + 1 if 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 !Atime setvar stayinloop!Dfid false endif endif endwhile

setvar PORTLDN 21

file port;dev=!PORTLDN

continue abortio !PORTLDN > $null

continue autodial.jpak;info="!JobName !UserName !AcctName"

continue abortio !PORTLDN > $null

purge autolock



deletevar stayinloop!Dfid deletevar cnt!Dfid

echo AUTODIAL.XEQ !JobPreFix!JobNo END !HPDATEF !HPTIMEF

setjcw cierror 0

Modify this script file appropriately, as described in the System setup in this chapter, andthen name it.

In the MPE :XEQ scripts configuration, list the filename as one of the :XEQ files that will beexecuted 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 requiresomeone to be paged.

Selecting a modem

AutoDial may not be compatible with every modem. For example, there can be problems ifthe modem must have certain control signals supplied before it will go online with thecomputer system.

In some cases, the modem will not do anything until it is manually placed into terminalmode. 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 orcarrier signal. If the proper signal is not received in time, the modem may hang up the phoneline. Therefore, only pick a modem that can be controlled with characters placed in thedialing sequence.

Most Hayes-compatible modems will work well with AutoDial. These types of modems areeasiest to use because they have the simplest dialing syntax.

The original HP Support Link modem is difficult to enable. The later release of the HPSupport Link is a Hayes-compatible modem.

When accessed, most display pagers require tones to be sent to them, similar to the onescreated by a push-button phone.

Note: To achieve the best results with AutoDial, Nobix recommends use of an HP modemcable, Part # 92219Q or equivalent.

AutoDial in test modeThere is a special TEST entry point included in AUTODIAL.JPAK.NSD that allows testing ofAutoDial 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 logicaldevice. 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=LDN

AUTODIAL.JPAK.NSD –test

Note: The word test must be entered in lower-case letters.

AutoDial terminates automatically after dialing.

Error messages

The following messages appear on the system console.

Message Description

AUTODIAL: CANNOT OPEN PHONE FILE AutoDial cannot open the PHONE.PUB.NSD file. This filecontains job IDs and dialing sequences. Check to see thatthis file exists and that no lockwords or other security existsfor this file.

AUTODIAL: CANNOT OPEN *PORT AutoDial cannot open the PORT file as defined by the :FILEPORT;DEV= LDN command line. Make sure you have specifiedthe correct device and that the device is not in use byanother process. Check that the modem is sending DataSetReady to the HP3000 logical device.

AUTODIAL: NO SPECIFIC RECORDFOUND IN PHONE

When executing AutoDial, it could not find a matchingrecord in the PHONE.PUB file, which means AutoDial cannotperform its function for this spoolfile.

CANNOT OPEN PORT: DSR NOTAVAILABLE

Data Set Ready signal is not available from the modem;therefore, AutoDial cannot open communication to themodem. Check to ensure that DSR is always enabled on themodem or that the modem is connected to a non-modemcontrol type LDN.


Appendix B

The UNLOAD program

The UNLOAD.JPAK.NSD program allows system administrators to make global changes tothe configuration files contained within the CONFIGIX program. It performs the followingtasks:

• Output an editable ASCII version of the configuration files.

• Backup the following five configuration files found in the JPAK group:CONFIGFOLDERAFOLDERFFOLDERRFDISPLY

• Use the edited ASCII file as input to populate the five configuration files with data.

Any text editor that works with the HP3000 can view or edit the ASCII file.

You must be very familiar with entries and syntax contained in CONFIGIX to edit thisASCII file. Refer to Chapter 3, The CONFIGIX program for information aboutCONFIGIX 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.

Appendix B The UNLOAD program


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 categorynumber. 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 thevalue $FOLDERHEADER (Top-level)

Fields 3 and 4 except if theyhave the value $FOLDERHEADER

8 FOLDERR definitions(Report folders)

Field 2 Fields 3 through 8

9 FOLDERA definitions(Access security)

Field 2 Fields 3 through 6

10 FDISPLY definitions(Rarely occurs)

Do not modify



• Data in the fields following the :TEXT : field are surrounded by double quotes (“) in theASCII 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 inthat 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 isautomatically incremented.

The UNLOAD program creates a backup of the current configuration and loads the changesfrom the ASCII configuration file. The changes take effect immediately, even if JobPak isrunning.

Warning: UNLOAD does very little syntax error checking. If you load an ASCII file thathas syntax errors, you might cause damage to the configuration files. If this occurs, refer tothe 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.PUBThis 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 thenumber from step 4).This is the file that contains the most recent configuration backup.

The system restores the backup to the configuration files.

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 ASCIIconfiguration 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 1998

JobPak configuration

Type FileDes. Job/Sess User Account.Device Command ValueGLOBAL CHECKIF NUM 1GLOBAL CHECKIF NUM 0GLOBAL CHECKEOJ NUM 1GLOBAL 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 Chapter 3, The CONFIGIX program, Configuring retention management.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 commanddescribed in Chapter 3, The CONFIGIX program, Configuring reporting.

The reports can be produced either on microfiche or paper. For details, refer to Chapter 6,The STDLOG report, Printing specific accounts.

The sample which follows depicts portions of a large STDLOG report.

Appendix C Standard log reports




STDCOPY listing

This report is printed whenever JobRescue makes an automatic copy of a $STDLIST, asdirected by a Copy :FILE command entry in the Job processing options configuration. Fordetails, refer to Chapter 3, The CONFIGIX program, Configuring job-specific values.


Appendix D

Exception list reports

The Exceptions List is printed whenever JobRescue detects that a $STDLIST has an error orother exception.

The FILE command for EXCPTLST, which applies globally, can be found in the JobPakcontrol file. To override the global configuration, use the EXCPTLST :FILE command asdescribed in Chapter 3, The CONFIGIX program, Job-processing options.

Appendix D Exception list reports

N
obix JobRescue reference guide 126126


N


Index

A

Accesslogs, 53reports, 76security levels, 24, 33

Action Control Sheet, 106documenting errors, 106format, 106sample listing, 108

Addressessending messages, 23specifying, 25

Archived jobs, 10, 69restoring, 58

B

Backup configuration file, 118Banner page, 10, 19Beeper networks, 10, 110Bypass

processing of $STDLISTs, 30

C

Column freeze, reports, 80, 81Comment lines, 104CONFIGIX program, 13, 14Configuration file, 16, 116

access, 13CONFIGIX.JPAK.NSD, 14global configuration, 16job-specific configuration, 16menus, 15

configuration report, 118Console messages, 25

deactivating, 22CONTINUE logic, on/off, 31Copy

STDCOPY listing, 19, 124to output file, 48, 83

CPU time, 69

D

Defer printing, 103Define

MPE commands, 31, 105Deletion of spoolfiles, 30, 38Display

$STDLIST information, 62, 76length, screen configuration, 72, 75

Do at Startup, 26Documention of errors, 106

E

E-mail addresssender, 25

EOJs, checking, 18, 31

Index


Error checking, 17, 20controlling, 105resume, 19suspend, 19

Error detection, 20, 30, 105customizing, 27detection suspension, 19, 31error text strings, 28IF/THEN/ELSE logic, 18, 30missing error text strings, 28non-error text strings, 28

Error messages, 9, 10, 19, 20, 22, 31AutoDial, 115disable, 22receiving, 23sending, 23

Errors, documentation of, 106Exceptions List, 98, 105

record of errors, 106report sample, 125substitution values, 107variable names, 107

F

Finding text, 50Folders

displaying, 73locating, 73

FormatAction Control Sheet, 106STDLOG report, 97

G

Global commands, 15

H

Heading freeze, reports, 80, 81Help

technical support, 8with STATUS, 51

History, messages, 10HPDeskManager ID, 25

I

IBM job listings, 62, 98Index pages, STDLOG report, 40, 42, 97Indexing reports, 33, 34, 85Installation, JobRescue, 12

J

Job stats, 69JOBPAK.JPAK.NSD file, 12

Jobslisting, 53, 62, 76

Job-specific commands, 16

L

Line modecommand reference, 46parameters, 44

Lines, listing, 52, 79Logon ID, 32Logs, 53

accessing logs, 53creating STDLOG reports, 38date and time of, 66, 77finding a job in, 64, 78scheduling retention management, 39STDLOG.JPAK, 39

M

Machine name, ID, 32Merge

$STDLISTs, 39scheduling retention management, 97

MERGE.PUB file, 99Message output, 23

configuration, 17, 22disable, 23displaying, 55global, 22receiving, 23sending, 23

Messages, history of, 10, 55Missing error text strings, 28Modem selection, 114MPE command (JPAKCOM), 89MPE commands

CONTINUE logic, 19IF logic, 30, 105IF/THEN/ELSE logic, 18, 30TELL command, 30, 105XEQ scripts

contents of, 105disable global execution, 31Do at Startup, 26execute, 23, 32job-specific execution, 31

N

NMSDEFER script, 103Non-error text strings, 28

O

OPACTION.PUB.NSD file, 106

Index


OPTION.JPAK file, 105Output priority

printing deferral, 103

P

Paging environment, 110Parameters, Line mode (STATUS), 44PARMLINE.JPAK file, 105Passwords, 13Pattern matching, 33, 34, 85PHONE file

dialing sequence, 111job identification, 111record format, 111

Printby page, 84, 85deferral, 103device, 30spoolfiles, 18, 30STDLOG report, 99to MPE file, 85

Print width, 72Purge, 21

$STDLISTs, 21

R

READY state, 104Reflection environment, 73Report mode

access, 73line navigation, 79, 80viewing configuration, 75, 83

Reportingarchival, 10changing defaults, 102STDLOG, 39, 97

Reportsaccess, 38, 76changing screen configurations, 75column freeze, 81deleting, 36heading freeze, 81indexing, 33, 34, 85locating, 77print by page, 84viewing generations, 78

Resuming ElectroPage, 89Retention management

$STDLIST access, 53date & time of logs, 39deleted files, 38, 58displaying logs, 38, 62scheduling, 39

Retrieve archived files, 58

S

Saving configurations, 16Scheduling STDLOG reports, 97Screen configuration, 75Search

for character strings, 59, 60for jobs, 62, 77in the STDLOG report, 40, 97

Securitymodifying access, 32passwords, 13

Showfolder command, 46, 65Size, $STDLISTs, 18Sort sequences, indexing, 40, 42Spoolfile priorities, 21, 103Spoolfiles

delay examination, 104deletion of, 30, 38empty, 19foreign, 18printing, 30report versions, 29, 78resume examination, 89save options, 29suspend examination, 31, 96

STATS listing, 69STATUS

command reference, 46Line mode parameters, 44Report mode, 73starting, 73stopping, 73version number, 71

STDLISTsaccess to, 76archived, 11bypassing, 30comment lines, 104controlling examination phase, 105copy to MPE file, 19, 31defer printing, 103delay examination, 104deletion of files, 30, 38displaying information, 62EOJs, 18, 31error checking, 17, 20, 105examined, 62finding jobs, 64foreign, 18IBM job listings, 62, 98listing lines, 52, 79maximum line number, 18merge, 39MPE commands, 23open, 70

Index


output priority, 18printing, 124purging, 21reporting, 40, 42restoring archivals, 58security, 24STDCOPY listing, 19, 31, 124viewing, 73

STDLOG reportconfiguration, 40, 97creation of, 39deletion of files, 97error text strings, 28format, 97IBM job listings, 62, 98index of jobs, 98missing text strings, 98non-error text strings, 28printing, 99retention management, 38sample report, 120searching for text, 40, 97user-defined indexes, 40, 42, 98versions, 99

STDLOG.JPAK file, 39STOP command, 89Suspend examination, 31, 96System identification, 17, 25

T

TELL command, 30TELLUSER.JPAK file, 23Text examination, control of, 105Text strings

exceptions, 27, 62find, 50, 59, 60missing, 27, 62

U

UNLOAD program, 116

V

Variable name usage, OPACTION file, 105Variables, Line mode (STATUS), 44Version number, STATUS, 71Viewer, 73

screen configuration, 75

W

Width, maximum display length, 72, 75

jobresue reference guide - nobix › software › jrguide.pdfnobix, inc. shall not be liable for...

Documents