× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



This is the job log:

Job name . . . . . . . . . . :   QPGMR           User  . . . . . . :   PETERVI
Number . . . . . . . . . . . :   021199
Job description  . . . . . . :   QPGMR           Library . . . . . :   QGPL
MSGID      TYPE                    SEV   DATE       TIME       FROM PGM
LIBRARY     INST     TO PGM       LIBRARY      INST
CPF1124    Information             00    08/21/02   09:17:36   QWTPIIPP
QSYS        05FF     *EXT                      *N
                                     Message . . . . :   Job
021199/PETERVI/QPGMR started on 08/21/02 at 09:17:37
                                       in subsystem QPGMR in QSYS. Job entered
system on 08/21/02 at 09:17:37.
CPI1125    Information             00    08/21/02   09:17:36   QWTPIIPP
QSYS        02B7     *EXT                      *N
                                     Message . . . . :   Job
021199/PETERVI/QPGMR submitted.
                                     Cause . . . . . :   Job
021199/PETERVI/QPGMR submitted to job queue QPGMR in
                                       QGPL from job 020648/PETERVI/CISPV1. Job
021199/PETERVI/QPGMR was started
                                       using the Submit Job (SBMJOB) command
with the following job attributes:
                                       JOBPTY(5) OUTPTY(5) PRTTXT()
RTGDTA(QCMDB) SYSLIBL(RBTSYSLIB  QSYS
                                       QSYS2      QUSRSYS    QHLPSYS) CURLIB
(*CRTDFT) INLLIBL(QTEMP      PETERTEST
                                       AEROPGMTST AEROTSTOBJ AEROPGM    MAPMODT
MAPPTFT    AMALIBC    AERODTATST
                                       AMFLIBT    AMTLIBT    HRVTDTA    PRVTDTA
VTVDU      QGPL       YSYNON
                                       DOWNLOAD   AMMLIB) LOG(4 00 *NOLIST)
LOGCLPGM(*NO) INQMSGRPY(*RQD)
                                       OUTQ(QUSRSYS/PRTHLD) PRTDEV(PRTHLD) HOLD
(*NO) DATE(*SYSVAL) SWS(00000000)
                                       MSGQ(QUSRSYS/PETERVI) CCSID(65535) SRTSEQ
(*N/*HEX) LANGID(ENU) CNTRYID(US)
ALWMLTTHD(*NO).
*NONE      Request                       08/21/02   09:17:36   QWTSCSBJ
*N       QCMD         QSYS         019E
                                     Message . . . . :  -CALL PGM(FI050C) PARM
('073102')
QWM2392    Diagnostic              00    08/21/02   09:17:37   QQXCI
QSYS        03FF     QQXBLDIF     QSYS         003C
                                     Message . . . . :   Query derived from
*QRYDFN object FI041Q1 in PETERTEST,
                                       code 00.
                                     Cause . . . . . :   You requested
information from a query management query
                                       (*QMQRY object) that could not be found
in the library or library list
                                       specified. This caused the object to be
temporarily created from a Query/400
                                       query definition (*QRYDFN object) with
the same name in library PETERTEST.
                                       The return code is 00. The following
return codes are possible: 00 - The
                                       derived query has no defects caused by
conversion. 10 - (Reserved) 20 - The
                                       derived query may be defective but is
usable. 30 - The derived query may be
                                       incomplete and/or unusable. The return
code is not intended to indicate
                                       anything about the differences to be
expected when running the derived
                                       query. Recovery  . . . :   If the request
involved running the query,
                                       inspect the report or database file
records carefully for differences. Some
                                       differences possible include: - Data from
*FIRST member instead of specified
                                       file member - Matched records join
instead of type of join expected - Loss
                                       of columns or different column order -
Different record order or selection
                                       set - Different length or precision of
result field data columns - Different
                                       values or unexpected numeric overflow in
result fields - Different values or
                                       unexpected numeric overflow of sums or
averages - Introduction of divide by
                                       zero errors for numeric calculations Use
the ANZQRY command for details
                                       about predictable differences. Read the
online help information for the
                                       ANZQRY command and pay special attention
to the information about generic
                                       (undiagnosed) differences. When the
ANZQRY command completes, check the
                                       second level message text for possible
differences that could result from
                                       diagnosed adjustments.
QWM2704    Diagnostic              00    08/21/02   09:17:42   QQXCLSTQ
QSYS        02D3     FI050C       PETERTEST    001B
                                     Message . . . . :   STRQMQRY command
completed using derived information.
                                     Cause . . . . . :   Information was derived
from a Query/400 query definition
                                       and used instead of at least one query
management object that could not be
                                       found.  The Query/400 query definition
was found using the names specified
                                       for locating the query management object.
Recovery  . . . :   Refer to the
                                       job log for the name and object type
specific message for each instance in
                                       which information had to be derived.
CPF2105    Escape                  40    08/21/02   09:17:42   QLIDOBJD
QSYS        064E     FI050C       PETERTEST    0021
                                     Message . . . . :   Object FI041Q1F in
QTEMP type *FILE not found.
                                     Cause . . . . . :   No object was found for
the name or type specified.
                                       Recovery  . . . :   Specify the correct
name or type of the object. Then try
                                       the request again.
CPA0701    Sender copy             99    08/21/02   09:17:42   QCLXERR
QSYS        00DA     QCLXERR      QSYS         00DA
                                     Message . . . . :   CPF2105 received by
FI050C at 3000. (C D I R)
                                     Cause . . . . . :   Control language (CL)
program FI050C in library PETERTEST
                                       detected an error at statement number
3000. Message text for CPF2105 is:
                                       Object FI041Q1F in QTEMP type *FILE not
found. Recovery  . . . :   This
                                       inquiry message can be avoided by
changing the program. Monitor for the
                                       error (MONMSG command) and perform error
recovery within the program. To
                                       continue, choose a reply value. Possible
choices for replying to message . .
                                       . . . . . . . . . . . . . :   C -- Cancel
the CL program. D -- Dump the CL
                                       program variables and cancel the CL
program. I -- Ignore the failing
                                       command. R -- Try the failing command
again.
*NONE      Reply                         08/21/02   09:18:10   QMHSCLVL
QSYS        0590     QCLXERR      QSYS         00E7
                                     Message . . . . :   C
CPF9999    Escape                  40    08/21/02   09:17:42   QMHUNMSG
*N       QCMD         QSYS         01CC
                                     Message . . . . :   Function check. CPF2105
unmonitored by FI050C at statement
                                       3000, instruction X'0021'.
                                     Cause . . . . . :   An escape exception
message was sent to a program which
                                       did not monitor for that message. The
full name of the program to which the
                                       unmonitored message was sent is FI050C  .
At the time the message was sent
                                       the program was stopped at higher level
language statement number(s) 3000.
                                       If more than one statement number is
shown, the program was a bound program.
                                       Optimization does not allow a single
statement number to be determined. If
                                       *N is shown as a value, it means the
actual value was not available.
                                       Recovery  . . . :   See the low level
messages previously listed to locate
                                       the cause of the function check.  Correct
any errors, and then try the
                                       request again.
CPC2402    Completion              50    08/21/02   09:18:10   QCMD
QSYS        0610     *EXT                      *N
                                     Message . . . . :   Job ended. Cancel
message received at command processor.
                                     Cause . . . . . :   A message with a
severity equal to or exceeding the end
                                       severity was received at the command
processor. Recovery  . . . :   See the
                                       messages previously listed to determine
the message that caused the job to
                                       be ended. Correct the errors, and then
try the request again.
CPF1164    Completion              00    08/21/02   09:18:10   QWTMCEOJ
QSYS        00AA     *EXT                      *N
                                     Message . . . . :   Job
021199/PETERVI/QPGMR ended on 08/21/02 at 09:18:11; 3
                                       seconds used; end code 20 .
                                     Cause . . . . . :   Job
021199/PETERVI/QPGMR completed on 08/21/02 at 09:18:11
                                       after it used 3 seconds processing unit
time.  The job had ending code 20.
                                       The job ended after 1 routing steps with
a secondary ending code of 0.  The
                                       job ending codes and their meanings are
as follows:  0 - The job completed
                                       normally. 10 - The job completed normally
during controlled ending or
                                       controlled subsystem ending. 20 - The job
exceeded end severity (ENDSEV job
                                       attribute). 30 - The job ended
abnormally. 40 - The job ended before
                                       becoming active. 50 - The job ended while
the job was active. 60 - The
                                       subsystem ended abnormally while the job
was active. 70 - The system ended
                                       abnormally while the job was active. 80 -
The job ended (ENDJOBABN command).
                                       90 - The job was forced to end after the
time limit ended (ENDJOBABN
                                       command). Recovery  . . . :   For more
information, see the Work Management
                                       book, SC41-5306.


PETER VIDAL
PALL Aeropower Corp. / SR Programmer Analyst
Website: www.pall.com  / Email: Peter_Vidal@Pall.com
Phone: 727-539-8448, x2414




As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.