Information Systems:System i Operations

2015-09-08T19:14:40Z

172.30.19.101: /* System Messages */

This computer has had several different names. They may be used interchangeably here, and when looking up information on the internet. The names are AS/400, iSeries, System i, and just plain i.

== Command line ==

A ‘command line’ allows you to key in commands or programs. Depending on where you are, it looks something like this –

Selection or command
===> ________________________________________________________________________________
_____________________________________________________________________________________

Or this –

Parameters for options 1, 2, 3 or command
===> ________________________________________________________________________________

== Library List ==

Objects on the i are grouped together in ‘libraries’; which are similar to ‘directories’, or ‘folders’ on a PC, except have only one level. A ‘library list’ is like a ‘path’; it tells the operating system where to look for requested objects.

To see your library list, key in DSPLIBL and press enter.

- Libraries that begin with ‘Q’ are supplied by IBM. (It is a bad idea to start with ‘Q’ when you are building your own objects.)

- ‘QTEMP’ is only accessible by the current job, and will be deleted when it ends. Temporary files can be put here so that they do not have to be implicitly deleted at job end. If work files are put here, each job will have its own data; instead of data for multiple jobs getting mixed together.

- ‘UWDQSYS’ contains objects that we have created, and want available to all users and jobs. As it is first in the library list, we can have our own versions of system objects. For example, program QSTRUP is called by the IPL. We have made changes to it to start up all our applications. It exists in both UWDQSYS and QSYS. Because UWDQSYS comes first in the library list, our customized version is called.

- Each ASW company has its own data libraries – they are changed in the library list when you change companies (green in the following list).

- ASW programs that we change or fix are in XX2480BP (purple), so that they are called instead of the base ASW programs. To test programs without affecting production, we would insert the test library before XX2480BP.

- Base ASW program libraries begin with ‘A’ (original, from Europe) or ‘U’ (modified in the U.S. for North America), then the version number. Notice that subsequent versions are higher in the library list, so that the latest release of a program will be called.

Display Library List
System: BART

5=Display objects in library

ASP
Opt Library Type Device Text
UWDQSYS SYS uniPharm - Custom - System Objects
QSYS SYS System Library
QSYS2 SYS System Library for CPI's
QHLPSYS SYS
QUSRSYS SYS System Library for Users
QTEMP USR
UP1480BFVA USR ASW PRODUCTION DATA FILE LIBRARY
UP1480BS USR ASW system objects for environment UP14
XX1480BP USR ASW rel XX1:480B UWD Extensions (non AS
XX2480BP USR ASW rel XX2:480B object library
UP1480BP USR Aldon/CMS IBS/ASW450/UP1480B (PDN)
U480BP USR Aldon/CMS IBS/ASW450/U480B (PDN)
U480AP USR Aldon/CMS IBS/ASW450/U480A (PDN)
CVT454AP USR ASW rel A:454A Appl CVT object library
A454AP USR ASW rel A:454A object library
A453AP USR ASW rel A:453A object library
A452AP USR ASW rel A:452A object library
A450AP USR ASW rel A:450A object library
QGPL USR General Purpose Library
RCSUTILPRD USR RCS -- Utility Objects and Data -- Prod
UWDASWPRDD USR UWD -- Extensions - VA - Data
UWDASWPRDP USR UWD -- Extensions - Production -- Objec
TLABARCODE USR T.L. Ashford & Associates Barcode400
WEBPRDD USR Web -- Data -- Production
WEBPRDP USR Web -- Programs -- Production
UWDUTILPRD USR UWD -- Extensions -- Common Utilities -
UNIPHARMIT USR UniPHARM IT Tools -- Includes Source

== Menus ==

Menus are a way of grouping together related commands or programs. If you know the name, you can go directly there by keying in GO <menu name> on the command line. In ASW the menu name is in the upper right corner in the green screen, and is the last word on the top line of the GUI. This doesn’t work in Extensions, as it uses a custom menu system.

== Commands ==

As a rule (of course there are exceptions), commands are made up of three character abbreviations; usually the first letter, then the next two consonants. For example, ‘work with active jobs’ is WRKACTJOB (there aren’t two consonants in JOB after the first letter). An exception is that ‘file’ is typically just ‘F’; as in WRKSPLF (work with spool files), and CPYF (copy file).

This makes it possible for you to guess a command. For example, perhaps you want to send someone a message. The code for this is ‘MSG’. All related commands are grouped together on menus, which are named ‘CMD’ plus the code. So to see all message commands, key in GO CMDMSG and press enter.

When you find what you think is the correct command, key in that menu option and press enter. The command will not be executed; its prompt screen will be displayed. Move the cursor to the name of the command (first line on the screen), and press F1. This will tell you what the command does, and what parameters are needed. Make sure to use F12 to exit back to the menu – not Enter – if you don’t want to execute the command.

== Print (or Spool) Files ==

=== View by User ===

To see a particular user’s print jobs that have not yet been printed, key in the command WRKSPLF <user ID> and press enter. To see your own, just key in WRKSPLF.

Work with All Spooled Files

Type options, press Enter.
1=Send 2=Change 3=Hold 4=Delete 5=Display 6=Release 7=Messages
8=Attributes 9=Work with printing status

Device or Total Cur
Opt File User Queue User Data Sts Pages Page Copy
_ FLR202P EODJOB QPRINT FLR202 HLD 2 1
_ FMR065P EODJOB QPRINT FMR065 HLD 1 1
_ FMR050P EODJOB QPRINT FMR050 HLD 1 1
_ GCFP852 EODJOB QPRINT GCFR852 HLD 2 1
_ FKR050P EODJOB QPRINT FKR050 HLD 2 1
_ WMR251P EODJOB PRT01 WMR251 HLD 1 1
_ WMR251P EODJOB PRT01 WMR251 HLD 1 1
_ GCFP852 EODJOB QPRINT GCFR852 HLD 2 1
_ FLR202P EODJOB QPRINT FLR202 HLD 2 1
More...
Parameters for options 1, 2, 3 or command
===> ____________________________________

F3=Exit F10=View 4 F11=View 2 F12=Cancel F22=Printers F24=More keys

Press F11 to see the date and time the spool file was created. Use option 5 to look at the file.

===Send to Printer===

If you want to print the file but ‘Device or Queue’ is QPRINT or PRT01, use option 2 to change to an output queue that is attached to a physical printer. (The next section of this manual explains what output queues are.)

Change Spooled File Attributes (CHGSPLFA)

Type choices, press Enter.

Spooled file . . . . . . . . . . > QPTAPDSP Name, *SELECT
Job name . . . . . . . . . . . . > DSPTAPE Name, *
User . . . . . . . . . . . . . > EODJOB Name
Number . . . . . . . . . . . . > 298072 000000-999999
Spooled file number . . . . . . > 1 1-999999, *ONLY, *LAST, *ANY
Job system name . . . . . . . . > BART Name, *ONLY, *CURRENT, *ANY
Spooled file created:
Creation date . . . . . . . . > 12182014 Date, *ONLY, *LAST
Creation time . . . . . . . . > 045916 Time, *ONLY, *LAST
Printer . . . . . . . . . . . . *OUTQ Name, *SAME, *OUTQ
Print sequence . . . . . . . . . *SAME *SAME, *NEXT
Form type . . . . . . . . . . . *STD Form type, *SAME, *STD
Copies . . . . . . . . . . . . . 1 1-255, *SAME
Restart printing . . . . . . . . *STRPAGE Number, *SAME, *STRPAGE...

More...
F3=Exit F4=Prompt F5=Refresh F10=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

Not on the first screen, where is says ‘*OUTQ’, but on the second page. So press page down.

Change Spooled File Attributes (CHGSPLFA)

Type choices, press Enter.

Additional Parameters

Output queue . . . . . . . . . . > ELAHO Name, *SAME, *DEV
Library . . . . . . . . . . . *LIBL Name, *LIBL, *CURLIB

Bottom
F3=Exit F4=Prompt F5=Refresh F10=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

Key in the name of the printer you want (for physical printers, the output queue has the same name as the printer). Clear the library name, and press enter. *LIBL will be inserted, so the library list will be used to find the queue. Press enter again.

Then check the ‘Sts’ column. If it says HLD (held), the entry will have to be released with option 6.

===View All Print Files===

To see all print jobs that have not yet printed, key in the command WRKOUTQ.

This will show all the output (or printer) queues, how many print jobs there are for each, and the status.

Work with All Output Queues

Type options, press Enter.
2=Change 3=Hold 4=Delete 5=Work with 6=Release 8=Description
9=Work with Writers 14=Clear

Opt Queue Library Files Writer Status
_ OMMQ OMMPRD 0 RLS
_ AIPQUEUE QGPL 0 RLS
_ ASWPICKLST QGPL 1378 RLS
_ ASWPUTAWAY QGPL 0 RLS
_ ASWSOREDI QGPL 916 RLS
_ ASWTSTWHSQ QGPL 0 RLS
_ ASW4DEV QGPL 0 RLS
_ CONVERSION QGPL 0 RLS
_ ELAHO QGPL 5 ELAHO RLS
_ GARBAGE QGPL 0 RLS
_ JIMH QGPL 0 RLS
_ LEX420 QGPL 0 LEX420 RLS

Use option 5 to see what print jobs are in a particular queue.

Work with Output Queue

Queue: ELAHO Library: QGPL Status: RLS/WTR

Type options, press Enter.
1=Send 2=Change 3=Hold 4=Delete 5=Display 6=Release 7=Messages
8=Attributes 9=Work with printing status

Opt File User User Data Sts Pages Copies Form Type Pty
_ RWRP191 FINADMIN RWRR191 HLD 69 1 *STD 5
_ Z3DP101 PAULAE Z3DR101 HLD 1 1 *STD 5
_ Z3DP101 PAULAE Z3DR101 HLD 1 1 *STD 5
_ Z3DP101 PAULAE Z3DR101 HLD 1 1 *STD 5
_ DIR271P JOHNT DIR271 HLD 426 1 *STD 5

===Output Queues===

‘Work With All Output Queues’ shows all the output queues. This can be many things –

Staging area for reports to be printed. This can be determined by the fact there is a ‘writer’ attached to the queue.

__ DCOFFICE QGPL 0 DCOFFICE RLS
__ ELAHO QGPL 4 ELAHO RLS

Holding area for reports that are to be deleted. Some reports are generated, but are never printed. They are cancelled during the end of day process. You can tell which these are because there is no writer attached, and if you use option 5 to see the files, then press F11, all the create dates will be today.

__ ASWPICKLST QGPL 585 RLS
__ ASWPUTAWAY QGPL 0 RLS
__ ASWSOREDI QGPL 558 RLS

Holding area for reports that aren’t to be printed, but are archived. Some reports are not printed, but are saved in case they are needed in the future. You can tell which these are because there is no writer attached, and if you use option 5 to see the files, then press F11, there will be some old create dates. For example, queues starting with ‘FIN’, in the library ‘FINANCE’, or ‘EDI’ in the library ‘QUSRSYS’.

__ FININVREG FINANCE 2313 RLS
__ FININVVAL FINANCE 562 RLS
__ FIN201506 FINANCE 11 RLS
__ FIN201507 FINANCE 11 RLS

Conduit to send reports to Jet Forms. These are not attached to printers, but instead to the server that runs Jet Forms. You can tell this by using option 2, then F10, and seeing –

Remote system . . . . . . . . . *INTNETADR Character value, *SAME...

Remote printer queue . . . . . . 'JFSRVR' Character value, *SAME...

__ JFHOLD QUSRSYS 3 HLD
__ JFPIPE QUSRSYS 538 JFPIPE RLS
__ JFSTMTS QUSRSYS 0 JFSTMTS RLS
__ JFTEST QUSRSYS 0 JFTEST HLD

Printer definition for Jet Forms. These are printers that are not used directly by the i, but have to be defined so that their names can be used to tell Jet Forms where to print invoices. For more information, see the section on ‘Jet Forms’.

__ L90INV08B QUSRSYS 0 L90INV08B RLS
__ NARINV09A QUSRSYS 0 NARINV09A RLS
__ OTCINV02A QUSRSYS 0 OTCINV02A RLS

'''Status (Sts)'''

RDY (Ready) - The file is available to be written to an output device by a writer.

OPN (Open) - The file has not been completely processed and is not ready to be selected by a writer.

DFR (Deferred) - The file has been deferred from printing.

SND (Sending) - The file is being or has been sent to a remote system. If this status lasts more than a few seconds it indicates a problem (unless it is an unusually large print job).

CLO (Closed) - The file has been completely processed by a program.

HLD (Held) - The file has been held.

SAV (Saved) - The file has been written and then saved. This file will remain saved until it is released or deleted.

WTR (Writer) - This file is currently being produced by the writer on an output device.

PND (Pending) - The file is pending to be printed.

PRT (Printing) - The file has been completely sent to the printer but print complete status has not been sent back.

MSGW (Message Waiting) - This file has a message which needs a reply or an action to be taken.

=== Problems ===

If there is a problem with a printer, find it on the list displayed by WRKOUTQ. If the number of files is zero, there is nothing waiting to print, so the problem is elsewhere. If the status is HLD (held), it must be released (option 6). If there is not a writer shown, restart it with option 2, enter, enter.

Use option 5 on the output queue to see the spooled files waiting, and look at the status of the top one. If it is status HLD (held), or SAV (saved), there is nothing waiting to print, so the problem is elsewhere. If it is SND (sending) or WTR (writer), and stays like that, the data is not getting to the printer. If it is MSGW (message waiting) there is a message waiting to be answered, for QSYSOPR. If it is RDY (ready) Use option 9 (work with printing status) and press enter. This may tell you something useful. Try option 2 (change status).

==Jobs==

There are basically two types of user jobs on the iSeries – interactive and batch. An interactive job is one that runs on a workstation, and requires interaction with a user. A batch job involves no user interaction, but requires more disk access and processor time. There is no reason for it to tie up a workstation.

The two types are handled differently by the system. Interactive jobs have a higher priority, but a smaller time slice. When the user presses a key, the system responses immediately and performs the request; which typically can be completed in the short time allowed. Then while it waits for the user to press another key, other jobs are serviced. If a job that should be batch (ie user interaction is not required, but there is a lot of disk access) is run interactively, the higher priority could degrade overall system performance, while the short time slice will not allow the job to run efficiently. (I once had a query that took 20 minutes to run interactively, and 2 minutes to run in batch.)

Note that while ASW jobs typically submit to batch when you press enter, you can press F2 to run them interactively. The advantages are that they will run immediately instead of lining up to run in batch, and that if the job is having problems, there will be a job log to review.

===Job Queues===

Key in the command WRKJOBQ to see the job queues, or the ‘lineup’ of jobs waiting for batch processing. These are jobs that have not yet started running.

Work with All Job Queues

Type options, press Enter.
2=Change 3=Hold 4=Delete 5=Work with 6=Release
8=Work with job schedule entries 9=Description 14=Clear

Opt Queue Library Jobs Subsystem Status
_ EOXBATCH QGPL 0 QBATCH RLS
_ IMPJOBQ QGPL 0 RLS
_ QBASE QGPL 0 RLS
_ QBATCH QGPL 0 QBATCH RLS
_ QBATCH1 QGPL 0 QBATCH RLS
_ QBATCH2 QGPL 0 QBATCH RLS
_ QBATCH3 QGPL 0 QBATCH RLS
_ QFNC QGPL 0 RLS
_ QINTER QGPL 0 QINTER RLS
_ QPGMR QGPL 0 QPGMR RLS
_ QSNADS QGPL 0 QSNADS RLS
_ QSPL QGPL 0 QSPL RLS
_ QSTATEMENT QGPL 0 QBATCH RLS
_ QS36EVOKE QGPL 0 QBATCH RLS
_ QS36MRT QGPL 0 QINTER RLS
_ QTXTSRCH QGPL 0 QBATCH RLS
_ QTCP QTCP 0 RLS
- DOMINO00 QUSRNOTES 0 DOMINO00 RLS
_ EMAIMPPRD UNIPHARMIT 54 EMASUBPRD RLS

The queues to worry about are QBATCH and QBATCH3. These are the line-ups of jobs submitted by users. If jobs start accumulating here, it could indicate a problem in the QBATCH subsystem – or that there are a couple of long running jobs running (each of these queues will submit two jobs at a time). This can happen just after the end of the month.

Job queue EMAIMPPRD will get a line-up of submitted jobs because of the way it is started every morning. These can be cancelled.

===Active Jobs===

To see all jobs that are currently running, key in the command WRKACTJOB.

Keep an eye on overall CPU % (5 to 20% is usual during the day). Press F5 to recalculate the usage over the length of time elapsed. Be aware of allowing the elapsed time to get too long, as the CPU % will start becoming more of an average than an actual figure. Press F10 to restart the elapsed time.

Each job also has a field indicating CPU %. For interactive jobs it is normally between 0 and 9% - it can peak as high as 60% but only for very short periods of time (press F10 to recalculate). If this percentage stays high, it could be a ‘runaway job’ (either a program that is in a loop, or a job that is no longer connected to a workstation, but is desperately trying to reconnect to it), or it could mean that the user is running a job interactively that should be run in batch. (In ASW pressing F2 will run a job online instead of submitting it to batch.) A batch job running online should be left to complete normally; a runaway job must be cancelled.

Individual batch jobs can use as much as 50 to 70% of the CPU without degrading performance. The QBATCH subsystem is tuned in such a way as to use all unused processor power. However, it has a lower run priority than QINTER, and so will defer to interactive jobs requiring processor time.

If the overall CPU % is high, the easiest way to find the culprit is to sort on the jobs’ percentages. Place the cursor in the CPU % column and press F16 (upper shift F4) to sort on this column from high to low. This will work for any column on the display – it does not work like windows; pressing F16 a second time will not reverse the sort sequence. Positioning the cursor under the ‘S’ or ‘u’ in Subsystem/Job will sort by subsystem then job; positioning it under any other letter will sort by job only.

===Subsystems and Jobs===

The DCRF subsystem shows all the RF guns that have a user signed on. (Interesting note – RFOSIGNON is for users who are only allowed to sign on to an RF gun. RFSIGNON will detect if the user is on an RF gun or a green screen, and go to either DCRF or QINTER, and run the required program.)

The advantage in having a separate subsystem, is that we can shut down picking in the warehouse, without affecting users in the office.

Work with Active Jobs BART
06/23/05 16:01:31
CPU %: 11.2 Elapsed time: 00:00:11 Active jobs: 446

Type options, press Enter.
2=Change 3=Hold 4=End 5=Work with 6=Release 7=Display message
8=Work with spooled files 13=Disconnect ...

Opt Subsystem/Job User Type CPU % Function Status
DCRF QSYS SBS .0 DEQW
RFTER0002A LEWISJ INT .0 PGM-RFSIGNON DSPW
RFTER0003A NATALIYAP INT .0 PGM-RFOSIGNON DSPW
RFTER0006A ALEXG INT .0 PGM-RFOSIGNON DSPW
RFTER0007A GORDONM INT .0 PGM-RFSIGNON DSPW
RFTER0008A MICHAELL INT .0 PGM-RFOSIGNON DSPW
RFTER0010A BIDOS INT .0 PGM-RFOSIGNON DSPW
RFTER0011A ERICC INT .0 PGM-RFOSIGNON DSPW
RFTER0012A VICTORIAM INT .0 PGM-RFOSIGNON DSPW
RFTER0013A JAMESS INT .0 PGM-RFOSIGNON DSPW
RFTER0014A MITAP INT .0 PGM-RFOSIGNON DSPW
RFTER0015A ELENAP INT .0 PGM-RFOSIGNON DSPW
RFTER0018A ANDYT INT .0 PGM-RFOSIGNON DSPW
RFTER0019A MELQUIADEM INT 3.6 PGM-RFOSIGNON DSPW
RFTER0020A JESUSAS INT .0 PGM-RFOSIGNON DSPW
RFTER0022A PARMJITG INT .0 PGM-RFOSIGNON DSPW
RFTER0024A MOHAMMEDR INT .0 PGM-RFOSIGNON DSPW
RFTER0026A INDERJITD INT .0 PGM-RFOSIGNON DSPW
RFTER0027A RENATON INT .0 PGM-RFOSIGNON DSPW
RFTER0029A PAULOV INT .0 PGM-RFOSIGNON DSPW
RFTER0030A CHOOSY INT .2 PGM-RFOSIGNON DSPW

The DOMINO subsystem shows the jobs to do with Lotus Notes.

DOMINO00 QSYS SBS .0 DEQW
ADMINP QNOTES BCI .6 PGM-ADMINP SELW
AMGR QNOTES BCI .0 PGM-AMGR SELW
AMGR QNOTES BCI .0 PGM-AMGR SELW
AMGR QNOTES BCI .0 PGM-AMGR CNDW
AMGR QNOTES BCI .0 PGM-AMGR CNDW
CALCONN QNOTES BCI .0 PGM-CALCONN CNDW
COLSRV400 QNOTES BCI .0 PGM-COLSRV400 SELW
CONTROLLER QNOTES BCI .0 PGM-CONTROLLER JVAW
DECS QNOTES BCI .0 PGM-DECS SELW
DIRCAT QNOTES BCI .0 PGM-DIRCAT SELW
EVENT QNOTES BCI .4 PGM-EVENT SELW
HTTP QNOTES BCI 1.1 PGM-HTTP SELW
MTC QNOTES BCI .0 PGM-MTC SELW
QJVAEXEC QNOTES BCI 1.0 PGM-SERVER SELW
REPLICA QNOTES BCI .0 PGM-REPLICA SELW
ROUTER QNOTES BCI .0 PGM-ROUTER SELW
SCHED QNOTES BCI .0 PGM-SCHED SELW
SMTP QNOTES BCI .0 PGM-SMTP SELW
UPDATE QNOTES BCI .0 PGM-UPDATE SELW

These are the jobs to do with electronic order processing. EMASUBPRD runs a job that ‘wakes up’ every hour and checks for low order volumes. The next four subsystems run the processing for inbound messages, inbound message parsing, inbound order processing, and outbound messages. These jobs also snooze for a while, then wake up to process any available records.

‘Delay’ can function in two different ways – ‘16:59:00’ means to wake up at one minute before 5PM, and ‘120’ means to wake up in two minutes or 120 seconds.

EMASUBPRD QSYS SBS .0 DEQW
EMAIOPPRD EODJOB BCH .0 DLY-16:59:00 DLYW
IMPSUBPRD QSYS SBS .0 DEQW
IMPPOSTPRD EODJOB BCH .0 DLY-120 DLYW
IMSSUBPRD QSYS SBS .0 DEQW
IMSPOSTPRD EODJOB BCH .0 DLY-120 DLYW
IOPSUBPRD QSYS SBS .0 DEQW
IOPPOSTPRD EODJOB BCH .0 DLY-120 DLYW
OMSSUBPRD QSYS SBS .0 DEQW
OMSPOSTPRD EODJOB BCH .0 DLY-300 DLYW

‘Exodus’ communicates with PC’s running BCD software. ‘Catapult’ and ‘Websmart’ are both using different versions of Exodus. This will be fixed when we upgrade Catapult. (Note – WebSmart is the tool we use to generate free form RPG programs to run in a browser, and Catapult takes i output and generates a PDF file.)

EXODUS QSYS SBS .0 DEQW
EXSERVER EXODUS ASJ .0 TIMW
EXODUS51 QSYS SBS .0 DEQW
EXSERV51 EXODUS51 ASJ .0 SELW
QCMN QSYS SBS .0 DEQW
EXODUS CATPULTADM EVK .0 DEQW
EXODUS CATPULTADM EVK .0 SELW

The jobs in the monitor subsystems are started by the end of day, and run all day.

MSGMONITOR keeps an eye on the QSYSOPR message queue, and forwards any unexpected messages to the addresses in data areas MSGREC to MSGREC5 (in library UNIPHARMIT).

ATLAS_INT checks the FTP server for scan batches from Atlas Courier. When it finds them, it updates the shipment archive.

EDIMON_PRD will send any EDI files that are ready, and will look to see if SPS Commerce has any files ready for us to pick up and process.

FTP_ORDERS checks the FTP server to see if any stores have sent us orders.

ORDALLOCFL checks to see if stock has come in for any future orders, or special orders. If a regularly stocked item has gone out of stock, and there is a future order, this program will set the item so that when the stock does come in, the future orders will be filled first. It used to be possible for a regular order to come in and scoop the stock.

MONITOR QSYS SBS .0 DEQW
MSGMONITOR EODJOB BCH .0 PGM-OPMESSAGES MSGW
MONITOR2 QSYS SBS .0 DEQW
ATLAS_INT ATLAS BCH .0 DLY-20 DLYW
EDIMON_PRD EDIUSER BCH .0 PGM-EDCUP040 MSGW
FTP_ORDERS EODJOB BCH .0 PGM-AICUP010 MSGW
ORDALLOCFL EODJOB BCH .0 DLY-13:30:00 DLYW

QBATCH runs normal batch jobs that users have submitted. Up to two jobs will run at the same time from each job queue – after that they will line up (in QBATCH or QBATCH3 job queues) and wait for their turn. (The subsystem and the job queue in this case have the same name, but it doesn’t have to be that way.)

PUR_ORDER jobs may cause problems. Only one can run at a time, so when it starts it checks to see if another version is already running. If so, the second version will delay and wait for the first to end. If the first does not end because it is in error, the second one will stay in delay. If a third PO print jobs starts it will also go into delay and the QBATCH subsystem will be blocked until someone notices the problem and corrects it. Meanwhile all submitted jobs will line up in the QBATCH and QBATCH3 job queues.

If no one corrects this, at end of day the three active jobs will be cancelled when the subsystem is ended (the only harm will be the PO will not be faxed or emailed). Any jobs lined up (but not started) will run when the subsystem is restarted the next morning.

QBATCH QSYS SBS .0 DEQW
RUNQRY SHEILAV BCH .0 PGM-ASGC900 RUN
PUR_ORDER SCOTTZ BCH .0 PGM-ASGC900 RUN
UPD_UD_SST SHEILAV BCH 25.1 PGM-ASGC900 RUN

We have three web servers –

WEBINTER for InfoNet, which is our browser based system for internal use

WEBSMART which is the Web Order system for our shareholder and customer use.

WEBTEST which is our test system.

There is another server for administration. We don’t use it much, but since version 6.1, when Domino starts, all TCP/IP servers are started at the same time.

These are Apache servers. See the section ‘WebSmart / Apache HTTP (Web) Servers’ for more information.

The jobs running QZSRCGI (Common Gateway Interface is a standard method used to generate dynamic content for web applications) call the programs that have been written with WebSmart. Multiple iterations can be running: as many as are needed to fill requests.

QHTTPSVR QSYS SBS .0 DEQW
ADMIN QLWISVR BCI .0 JVM-com.ibm.lw THDW
ADMIN QTMHHTTP BCH .0 PGM-QZHBMAIN SIGW
ADMIN QTMHHTTP BCI .0 PGM-QZSRLOG SIGW
ADMIN QTMHHTTP BCI .0 PGM-QZSRHTTP SIGW
ADMIN2 QLWISVR BCI .0 JVM-com.ibm.lw THDW
ADMIN3 QLWISVR BCI .0 JVM-com.ibm.lw THDW
ADMIN4 QWEBADMIN BCI .4 JVM-/qibm/prod THDW
WEBINTER QTMHHTTP BCH .0 PGM-QZHBMAIN SIGW
WEBINTER QTMHHTTP BCI .0 PGM-QZSRLOG SIGW
WEBINTER QTMHHTTP BCI .0 PGM-QZSRLOG SIGW
WEBINTER QTMHHTTP BCI .0 PGM-QZSRHTTP SIGW
WEBINTER QTMHHTTP BCI .0 PGM-QZSRHTTP DEQW
WEBINTER QTMHHTP1 BCI .0 PGM-QZSRCGI TIMW
WEBINTER QTMHHTP1 BCI .0 PGM-QZSRCGI TIMW
WEBINTER QTMHHTP1 BCI .0 PGM-QZSRCGI TIMW
WEBINTER QTMHHTP1 BCI .0 PGM-QZSRCGI TIMW
WEBINTER QTMHHTP1 BCI .0 PGM-QZSRCGI TIMW
WEBINTER QTMHHTP1 BCI .0 PGM-QZSRCGI TIMW
WEBINTER QTMHHTP1 BCI .0 PGM-QZSRCGI TIMW
WEBINTER QTMHHTP1 BCI .0 PGM-QZSRCGI TIMW
WEBSMART QTMHHTTP BCH .0 PGM-QZHBMAIN SIGW
WEBSMART QTMHHTTP BCI .0 PGM-QZSRLOG SIGW
WEBSMART QTMHHTTP BCI .0 PGM-QZSRLOG SIGW
WEBSMART QTMHHTTP BCI .3 PGM-QZSRHTTP SIGW
WEBSMART QTMHHTTP BCI .0 PGM-QZSRHTTP DEQW
WEBSMART QTMHHTP1 BCI 5.3 PGM-QZSRCGI TIMA
WEBSMART QTMHHTP1 BCI 6.6 PGM-QZSRCGI TIMA
WEBSMART QTMHHTP1 BCI .0 PGM-QZSRCGI TIMW
WEBSMART QTMHHTP1 BCI .0 PGM-QZSRCGI TIMW
WEBSMART QTMHHTP1 BCI .0 PGM-QZSRCGI TIMW
WEBSMART QTMHHTP1 BCI .0 PGM-QZSRCGI TIMW
WEBSMART QTMHHTP1 BCI .0 PGM-QZSRCGI TIMW
WEBSMART QTMHHTP1 BCI .0 PGM-QZSRCGI TIMW
WEBSMART QTMHHTP1 BCI .0 PGM-QZSRCGI TIMW
WEBSMART QTMHHTP1 BCI .0 PGM-QZSRCGI TIMW
WEBSMART QTMHHTP1 BCI .0 PGM-QZSRCGI TIMW
WEBSMART QTMHHTP1 BCI .0 PGM-QZSRCGI TIMW
WEBTEST QTMHHTTP BCH .0 PGM-QZHBMAIN SIGW
WEBTEST QTMHHTTP BCI .0 PGM-QZSRLOG SIGW
WEBTEST QTMHHTTP BCI .0 PGM-QZSRHTTP SIGW
WEBTEST QTMHHTTP BCI .0 PGM-QZSRHTTP DEQW

All non-RF interactive sessions run in the QINTER subsystem. About the only thing to watch out for here is ‘runaway jobs’. This is either a program that is in a loop, or a job that is no longer connected to a workstation, but is desperately trying to reconnect to it.

QINTER QSYS SBS .0 DEQW
HABATERM GORDONM INT .0 PGM-RFSIGNON DSPW
OTCTERM GORDONM INT .0 PGM-RFSIGNON DSPW
QPADEV000B STEVENL INT .0 PGM-RFSIGNON DSPW
QPADEV000C NANCYN INT .0 PGM-UNITY DSPW
QPADEV000L MARYT INT .0 PGM-UNITY DSPW
+QPADEV000R MARYT INT .0 PGM-ASGC800 DSPW
+QPADEV000S RUBYS INT .0 PGM-ASGC800 DSPW
QPADEV001N SHANNONM INT .0 PGM-UNITY DSPW
QPADEV001P RUBYS INT .0 PGM-UNITY DSPW
QPADEV001Q RUBYS INT .0 PGM-UNITY DSPW
QPADEV001Z MARYC INT .0 PGM-UNITY DSPW
QPADEV0013 GORDONM INT .0 PGM-RFSIGNON DSPW

This subsystem runs the ASW direct jobs. The two characters after the underscore indicate the company (note VA for the main production company, and PL for test). Basically, these jobs control the flow of sales orders through the system.

UP1480BS QSYS SBS .0 DEQW
AMTRDR_PLA ASW4OWN BCH .0 PGM-ASGC900 DEQW
AMTRDR_PLT ASW4OWN BCH .0 PGM-ASGC900 DEQW
AMTRDR_PLT ASW4OWN BCH .0 PGM-ASGC900 DEQW
AMTRDR_VAA ASW4OWN BCH .0 PGM-ASGC900 DEQW
AMTRDR_VAT ASW4OWN BCH .0 PGM-ASGC900 DEQW
AMTRDR_VAT ASW4OWN BCH .0 PGM-ASGC900 DEQW
DPRQ1_PL ASW4OWN BCH .0 PGM-ASGC900 DEQW
DPRQ1_VA ASW4OWN BCH .0 PGM-ASGC900 DEQW
DPRQ2_PL ASW4OWN BCH .0 PGM-ASGC900 DEQW
DPRQ2_VA ASW4OWN BCH .0 PGM-ASGC900 DEQW
DPRQ3_PL ASW4OWN BCH .0 PGM-ASGC900 DEQW
DPRQ3_VA ASW4OWN BCH .0 PGM-ASGC900 DEQW
ORDFLOW_PL ASW4OWN BCH .0 PGM-ASGC900 DEQW
ORDFLOW_VA ASW4OWN BCH .0 PGM-ASGC900 DEQW

===Cancelling a Job===

In WRKACTJOB, find the job that is ‘runaway’, or perhaps the RF gun that is locked. Key ‘4’ in front of it, in the option field, and press F4.

End Job (ENDJOB)

Type choices, press Enter.

Job name . . . . . . . . . . . . > SHEILAV3 Name
User . . . . . . . . . . . . . > SHEILAV Name
Number . . . . . . . . . . . . > 101245 000000-999999
How to end . . . . . . . . . . . *CNTRLD *CNTRLD, *IMMED
Delay time, if *CNTRLD . . . . . 30 Seconds
Delete spooled files . . . . . . *NO *NO, *YES
Maximum log entries . . . . . . *SAME Number, *SAME, *NOMAX
Additional interactive jobs . . *NONE *NONE, *GRPJOB, *ALL

In the ‘How to end’ field, change *CNTRLD (controlled) to *IMMED (immediate). If you make the mistake of pressing Enter instead of F4, the job will go right into a controlled end. You can still go back and repeat this procedure, remembering this time to press F4.

==Data Files==

Data files are grouped together into libraries (like folders on PC’s, but only with a single level). These data libraries are -

'''Production''' '''Development'''
ASW UP1480BFVA UP1480BFPL
Extension UWDASWPRDD UWDASWVOLD
Web (web orders, InfoNet) WEBPRDD WEBDEVD

There are two types of data files; physical and logical. A physical file contains the actual data records. A logical file is not data, but an index to the data.

Logical files are defined to allow different programs to access the data in different ways; or to optimise SQL (see Programming / SQL – Structure Query Language for an explanation of this).

For example, SROITR (Inventory Transactions) is a physical file. Records are accessed in the sequence in which they were written. Some of the logical files, or indexes, are SRBITR (keyed by inventory event code, order number, line number), SR1ITR (item, warehouse, date, time, text, batch, quantity), SR2ITR (item, date, time, text, batch, quantity), SR12ITR (accounting period, item, warehouse), and SRYITR (warehouse, inventory event code, date, handler).

In ASW, the first two characters indicate the system (in this example 'Stock Room'). An ‘O’ for the third character means it is a physical file; ‘B’ or a number means logical file; other letters working backwards from Z are logical files we have built. The rest of the name indicates the type of data. In the extensions, the last character(s) indicate the type; P for physical, or L and a number for logical.

To find out if a particular file is physical or logical, and it logical what the physical file is, key in DSPFD SR2ITR and press enter.
Notice 'Type of file' 10 lines down, and 'Files accessed by logical file' in about the middle.

Display Spooled File
File . . . . . : QPDSPFD Page/Line 1/1
Control . . . . . Columns 1 - 130
Find . . . . . .
*...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8....+....9....+....0....+....1....+....2....+....3
3/26/15 Display File Description
DSPFD Command Input
File . . . . . . . . . . . . . . . . . . . : FILE SR2ITR
Library . . . . . . . . . . . . . . . . . : *LIBL
Type of information . . . . . . . . . . . . : TYPE *ALL
File attributes . . . . . . . . . . . . . . : FILEATR *ALL
System . . . . . . . . . . . . . . . . . . : SYSTEM *LCL
File Description Header
File . . . . . . . . . . . . . . . . . . . : FILE SR2ITR
Library . . . . . . . . . . . . . . . . . . : UP1480BFPL
'''Type of file . . . . . . . . . . . . . . . : Logical'''
File type . . . . . . . . . . . . . . . . . : FILETYPE *DATA
Auxiliary storage pool ID . . . . . . . . . : 00001
Data Base File Attributes
Externally described file . . . . . . . . . : Yes
File level identifier . . . . . . . . . . . : 1050129085518
Creation date . . . . . . . . . . . . . . . : 01/29/05
Text 'description' . . . . . . . . . . . . : TEXT Item/date/time/
stockroom/text/batch/qty
Distributed file . . . . . . . . . . . . . : No
Partitioned SQL Table . . . . . . . . . . . : No
DBCS capable . . . . . . . . . . . . . . . : No
Maximum members . . . . . . . . . . . . . . : MAXMBRS 1
Number of triggers . . . . . . . . . . . . : 0
Number of members . . . . . . . . . . . . . : 1
Access path maintenance . . . . . . . . . . : MAINT *IMMED
Access path recovery . . . . . . . . . . . : RECOVER *NO
Force keyed access path . . . . . . . . . . : FRCACCPTH *NO
Preferred storage unit . . . . . . . . . . : UNIT *ANY
Record format selector program . . . . . . : FMTSLR *NONE
Records to force a write . . . . . . . . . : FRCRATIO *NONE
Maximum file wait time . . . . . . . . . . : WAITFILE *IMMED
Maximum record wait time . . . . . . . . . : WAITRCD 60
With check option . . . . . . . . . . . . . : NONE
Allow read operation . . . . . . . . . . . : Yes
Allow write operation . . . . . . . . . . . : Yes
Allow update operation . . . . . . . . . . : ALWUPD *YES
Allow delete operation . . . . . . . . . . : ALWDLT *YES
Record format level check . . . . . . . . . : LVLCHK *YES
Access path . . . . . . . . . . . . . . . . : Keyed
Access path size . . . . . . . . . . . . . : ACCPTHSIZ *MAX1TB
Access path logical page size . . . . . . . : PAGESIZE *KEYLEN
Maximum key length . . . . . . . . . . . . : 98
Maximum record length . . . . . . . . . . . : 208
Access Path Description
Access path maintenance . . . . . . . . . . : MAINT *IMMED
Unique key values required . . . . . . . . : UNIQUE No
Key order . . . . . . . . . . . . . . . . . : Not specified
Select/omit specified . . . . . . . . . . . : No
Access path journaled . . . . . . . . . . . : No
Access path . . . . . . . . . . . . . . . . : Keyed
Number of key fields . . . . . . . . . . . : 7
Record format . . . . . . . . . . . . . . . : ITR
Key field . . . . . . . . . . . . . . . . : ITPRDC
Sequence . . . . . . . . . . . . . . . : Ascending
Sign specified . . . . . . . . . . . . : UNSIGNED
Zone/digit specified . . . . . . . . . : *NONE
Alternative collating sequence . . . . : No
Key field . . . . . . . . . . . . . . . . : ITDATE
Sequence . . . . . . . . . . . . . . . : Ascending
Sign specified . . . . . . . . . . . . : SIGNED
Zone/digit specified . . . . . . . . . : *NONE
Alternative collating sequence . . . . : No
Key field . . . . . . . . . . . . . . . . : ITTIME
Sequence . . . . . . . . . . . . . . . : Ascending
Sign specified . . . . . . . . . . . . : SIGNED
Zone/digit specified . . . . . . . . . : *NONE
Alternative collating sequence . . . . : No
Key field . . . . . . . . . . . . . . . . : ITSROM
Sequence . . . . . . . . . . . . . . . : Ascending
Sign specified . . . . . . . . . . . . : UNSIGNED
Zone/digit specified . . . . . . . . . : *NONE
Alternative collating sequence . . . . : No
Key field . . . . . . . . . . . . . . . . : ITTEXT
Sequence . . . . . . . . . . . . . . . : Ascending
Sign specified . . . . . . . . . . . . : UNSIGNED
Zone/digit specified . . . . . . . . . : *NONE
Alternative collating sequence . . . . : No
Key field . . . . . . . . . . . . . . . . : ITBATC
Sequence . . . . . . . . . . . . . . . : Ascending
Sign specified . . . . . . . . . . . . : UNSIGNED
Zone/digit specified . . . . . . . . . : *NONE
Alternative collating sequence . . . . : No
Key field . . . . . . . . . . . . . . . . : ITQTY
Sequence . . . . . . . . . . . . . . . : Ascending
Sign specified . . . . . . . . . . . . : SIGNED
Zone/digit specified . . . . . . . . . : *NONE
Alternative collating sequence . . . . : No
'''Files accessed by logical file PFILE
File Library LF Format
SROITR UP1480BFPL ITR'''
Sort Sequence . . . . . . . . . . . . . . . : SRTSEQ *HEX
Language identifier . . . . . . . . . . . . : LANGID ENU
Member Description
Member . . . . . . . . . . . . . . . . . . : MBR SR2ITR
Member level identifier . . . . . . . . . : 1050129085518
Member creation date . . . . . . . . . . : 01/29/05
Text 'description' . . . . . . . . . . . : TEXT Item/date/time/
stockroom/text/batch/qty
Expiration date for member . . . . . . . : EXPDATE *NONE
Access path maintenance . . . . . . . . . : MAINT *IMMED
Access path recovery . . . . . . . . . . : RECOVER *NO
Preferred storage unit . . . . . . . . . : UNIT *ANY
Record format selector program . . . . . : FMTSLR *NONE
Records to force a write . . . . . . . . : FRCRATIO *NONE
Share open data path . . . . . . . . . . : SHARE *YES
Access Path Activity Statistics . . . . . :
Access path logical reads . . . . . . . :
Access path physical reads . . . . . . :
Index size . . . . . . . . . . . . . . : 3315630080
Access path valid . . . . . . . . . . . : Yes
Implicit access path sharing . . . . . : Yes
Access path journaled . . . . . . . . : Yes
Number of unique partial key values . . :
Key field 1 . . . . . . . . . . . . . : 66959
Key fields 1 - 2 . . . . . . . . . . : 11624772
Key fields 1 - 3 . . . . . . . . . . : 23585801
Key fields 1 - 4 . . . . . . . . . . : 23742851
File owning access path . . . . . . . . : UP1480BFPL/SR18ITR
Member . . . . . . . . . . . . . . . . : SR18ITR
Shared access path attributes
Maintenance . . . . . . . . . . . . . : *IMMED
Access path recovery . . . . . . . . : *NO
Force keyed access path . . . . . . . : *NO
Keys must be unique . . . . . . . . . : No
Last change date/time . . . . . . . . . . : 01/17/15 15:29:30
Last save date/time . . . . . . . . . . . : 01/17/15 01:06:20
Last restore date/time . . . . . . . . . : 01/17/15 14:49:33
Last used date . . . . . . . . . . . . . : 02/12/15
Days used count . . . . . . . . . . . . . : 1
Reset date . . . . . . . . . . . . . . :
Number of data members . . . . . . . . . : 1
Based on file . . . . . . . . . . . . . . : SROITR
Library . . . . . . . . . . . . . . . . : UP1480BFPL
Member . . . . . . . . . . . . . . . . : SROITR
Logical file format . . . . . . . . . . : ITR
Number of index entries . . . . . . . . : 23756196
Record Format List
Record Format Level
Format Fields Length Identifier
ITR 36 208 3CDDB9F4542D1
Text . . . . . . . . . . . . . . . . . . . :
Total number of formats . . . . . . . . . . : 1
Total number of fields . . . . . . . . . . . : 36
Total record length . . . . . . . . . . . . : 208
Member List
Source Creation Last Change
Member Size Type Date Date Time
SR2ITR 3315630080 01/29/05 01/17/15 15:29:30
Text: Item/date/time/stockroom/text/batch/quantity
Total number of members . . . . . . . . . : 1
Total number of members not available . . : 0
Total of member sizes . . . . . . . . . . : 3315630080

This shows that SR2ITR is a logical file that is for the physical file SROITR.

==HMC Hardware Management Console==

This has many capabilities that we do not use. The reason we have it is to access the i from home, when it is in a restricted state (during overnight processing), or in error.

We connect to it through Client Access; but configured to go directly to it; not through the i. When not at uniPharm, the connection must go through the VPN.

===Create the Session===

Open the 5250 emulator on your PC

Create a new session

In the Configure PC5250 window, type hmc525.unipharm.local

Change port number to 2300 (no SSL) and use the Navigator default for security

Select Properties

Select ‘Use default User ID, prompt as needed’ from the drop-down box. Later versions may have ‘Use HMC 5250 Console Settings’ – if so, use it

Key Q#HMC into the User ID field

Select current SSL level = use Navigator default

Change the display size to 27x132

'''Create the Icon'''

New / iSeries Desktop Icon / PC5250 Emulator / hmc525.unipharm.local / change text as desired (Note: -- if you save to a folder and then move to the desktop, it will not work. Do not remove the .CAE icon that is added to your desk top at the same time; because then it will not work.)

===Log on===

Open the 5250 emulator

Select 11 = English

Log in as hscroot, NewVisionIT

Select the system, which should be 1

Select 2 = Shared session. Session key = our favorite password plus 198

The service tools user is qsecofr, the password is our favorite

Then log in as yourself or QSECOFR or EODJOB

==System Messages==

===Set up Message Display===

There are two difference formats in which messages can be displayed. Strangely enough, the ‘basic’ assistance level is much better than ‘intermediate’, so the first time you look at messages you may have to change your setting. On a command line, key in DSPMSG QSYSOPR and press enter.

If the display looks like this –

Display Messages
System: BART
Queue . . . . . : QSYSOPR Program . . . . : *DSPMSG
Library . . . : QSYS Library . . . :
Severity . . . : 99 Delivery . . . : *HOLD

Type reply (if required), press Enter.
Log version QHST13346A in QSYS closed and should be saved.
Cleanup of system journals and system logs started.
Cleanup of system journals and system logs successfully completed.
Cleanup has completed.
Writer 997043/QSPLJOB/RETPRT05 started.

Press F21 (press and hold Shift, then press F9). Key in 1, and press enter. The screen will change. The big advantage is that any message requiring an answer will be at the top of the list. At the ‘intermediate’ level, you have to page through all the messages to find them. (I don’t know why this inconvenient feature makes the level more advanced.)

Work with Messages
Messages in: QSYSOPR System: BART

Type options below, then press Enter.
5=Display details and reply

Opt Message
Messages needing a reply
5 Operator action required on device NARINV09A (C R).
Reply . . : R
Messages not needing a reply
_ Log version QHST13346B in QSYS closed and should be saved.
_ Writer 997429/QSPLJOB/RETPRT05 started.
_ Writer 997043/QSPLJOB/RETPRT05 ended normally.
_ Service Agent is analyzing your system product activity log entries.
_ Job message queue for 995992/EODJOB/FTP_ORDERS has been wrapped.

===Look at Message Detail===

For any message, whether or not it needs a reply, you can key a 5, and press Enter to see the details. You may have to press page down to see more.

Additional Message Information

Message ID . . . . . . : CPA403D Severity . . . . . . . : 99
Message type . . . . . : Inquiry
Date sent . . . . . . : 12/10/13 Time sent . . . . . . : 23:01:44

Message . . . . : Operator action required on device NARINV09A (C R).
Cause . . . . . : An error was detected on device NARINV09A. Look at the
printer to determine the cause of the problem.
Recovery . . . : Do one of the following and try the request again.
Possible choices for replying to message . . . . . . . . . . . . . . . :
C -- Enter C to cancel the writer.
R -- Enter R to continue printing the file after the problem at the printer
has been corrected.
Technical description . . . . . . . . : For more information, see your
printer's operator guide.
Bottom

F9 will show the job that issued the message. Depending on the message, that may or may not be useful. For example, this gives the Websmart program (IN_ITEMCHG) and function (DSPPRICES) that had an error. (Note that this is not linked to the previous example, but is an illustration.)

Display Message Details

Message ID . . . . . . : MCH1210 Severity . . . . . . . : 40
Date sent . . . . . . : 04/01/14 Time sent . . . . . . : 11:06:01
Message type . . . . . : Escape
From . . . . . . . . . : QTMHHTP1 CCSID . . . . . . . . : 65535

From program . . . . . . . . . : Q63DFE79CD
From library . . . . . . . . : QRPLOBJ
From module . . . . . . . . : IN_ITEMCHG
From procedure . . . . . . . : DSPPRICES0
From statement . . . . . . . : 12759

To program . . . . . . . . . . : Q63DFE79CD
To library . . . . . . . . . : QRPLOBJ
To module . . . . . . . . . : IN_ITEMCHG
To procedure . . . . . . . . : DSPPRICES0
To statement . . . . . . . . : 12759

More...
Press Enter to continue.

F1=Help F3=Exit F12=Cancel

===Respond to a Message Needing a Reply===

Perform whatever action the message suggests, then reply. The best answer, if it is offered, is always R for Retry. Otherwise I’m afraid it can be different for every event.

Additional Message Information

Message ID . . . . . . : CPA403D Severity . . . . . . . : 99
Message type . . . . . : Inquiry
Date sent . . . . . . : 12/10/13 Time sent . . . . . . : 23:01:44

Message . . . . : Operator action required on device NARINV09A (C R).
Cause . . . . . : An error was detected on device NARINV09A. Look at the
printer to determine the cause of the problem.
Recovery . . . : Do one of the following and try the request again.
Possible choices for replying to message . . . . . . . . . . . . . . . :
C -- Enter C to cancel the writer.
R -- Enter R to continue printing the file after the problem at the printer
has been corrected.
Technical description . . . . . . . . : For more information, see your
printer's operator guide.
Bottom
Reply . . . : R
Press Enter to continue.

F3=Exit F6=Print F9=Display message details F12=Cancel
F21=Select assistance level

===Display Message Details of an Error Code===

On a command line, key in DSPMSGD <msg ID>. For example, DSPMSGD CPF2817.

Select Message Details to Display
System: BART
Message ID . . . . . . . . . : CPF2817
Message file . . . . . . . . : QCPFMSG
Library . . . . . . . . . : QSYS
Message text . . . . . . . . : Copy command ended because of error.

Select one of the following:

1. Display message text
2. Display field data

5. Display message attributes

30. All of the above

Selection
__

F3=Exit F12=Cancel

If you cannot get to the i to see what the error is, you can Google the message ID – in this example CPA403D.

uniWIKI - User contributions [en]

Information Systems:System i Operations