AS/400 HELP

"CUEILOG2"

(QINTER LOG)

CUEILOG2 saves and displays a log of QINTER online job terminations. The exit point QIBM_QWT_JOBNOTIFY sends the job name to dtaq CUEILOG2 in library CUEINTER2 .

Program CUEILOG2 records job info into file CUEILOG2. API QDCRDEVD adds the IP address of the Telnet device.

Program QIHIST displays these records and allows you to select a particular user id.

CUEILOG2 was developed at V5r3 and takes advantage of the new date/time fields and processing time used field in qibm-qwt-jobnotify .

Please read and understand all the instructions below before installing CUEILOG2.

PC INSTRUCTIONS:

Download "CUEINTER2” to your PC.

Go to a DOS session and enter the following;

FTP SYSTEM (system = your AS/400’s name or IP address)

Enter a valid user id and password

CD QGPL

LCD C:\DIRECTORY (directory= the directory on your pc where you downloaded “ cueinter2.savf”

QUOTE SITE NAMEFMT 1

BIN

PUT CUEINTER2.SAVF

QUOTE RCMD RSTLIB SAVLIB(CUEINTER2) DEV(*SAVF) SAVF(QGPL/CUEINTER2)

 Note: If there is a security problem restoring all objects with the command above, sign on to your as/400 as Qsecofr and run RSTLIB from the command line.

AS/400 INSTRUCTIONS:

INSTALL SECTION; (1 time only after library CUEINTER2 is restored to the As/400)

ADDJOBQE SBSD(QSYS/QINTER) JOBQ(CUEINTER2/CUEILOG2) MAXACT(1) SEQNBR(NNN)

NNN = a unique sequence number. Use the command:

DSPSBSD SBSD(QSYS/QINTER) and take option 6. Use a Seq Nbr not already allocated.

WRKREGINF

Look for QIBM_QWT_JOBNOTIFY and take option 8

Enter 1 and enter Program 1 or a number higher than the highest exit program number currently used.

For fields; Program………… CUEILOG2

Library……… CUEINTER2

Hit F10 and roll up

For fields; Length of data……… 144

Program data 0002QINTER QSYS

NOTE: you must enter it exactly as above (0002QINTER followed by 4 spaces and QSYS)

NOTE This exit point will start working only AFTER QINTER has been stopped and restarted. Either wait for the next IPL or manually stop and restart QINTER.

STARTING AND STOPPING QUEILOG:

To start: CALL CUEINTER2/STARTQIL2

To End: CALL CUEINTER2/STOPQIL2

NOTE: Verify CUEILOG2 is working by entering command: WRKACTJOB. You should see CUEILOG2 running under QINTER.

NOTE: STARTQIL2 starts the CUEILOG2 program in Qinter and waits for a string of job name from the exit point or a string with the the word ‘QUIT’ (from STOPQIL2)

NOTE: STOPQIL2 sends the word ‘QUIT’ to CUEILOG2 which stops the program from processing dtaq records. If CUEILOG2 is not active records will collect in the dtaq and wait until CUEILOG2 is started again. Calling STOPQIL2 twice or more in succession will make it appear CUEILOG2 is not working as it will stop CUEILOG2 every time it goes through.

To display the log file……

ADDLIBLE CUEINTER2

CALL QIHIST

NOTE: Cueilog2 test each dtaq entry against the device description. If the device id does not match the IP address is not inserted. Also if a delay of 10 seconds or more occurs a ? is placed in the status field to signify that this IP address may not be the actual one. These two scenarios will occur if CUEILOG2 is not started as soon as sub system is started

NOTE: Field Proc Time is the field ‘Processimg Time Used’ provided by qibm_qwt_jobnotify. I divided it by 1000. This field indicates actual work performed by this user.

ERROR CODES

Blank Ok

30 session ended abnormally (signoff was not used)

for the other codes use WRKMSGF MSGF(QCPGMSG) position to CPF1164 and take option 5 and then 30