Default message destinations - syncsort_simulate_2000

The execution environment of the product and the rules language determine which method is used to write a message. This topic documents the default message destinations when the rules language or an internal product message is written without a specified destination.

The following sample rule demonstrates the default message destination. The rule issues a warning message for data set names that end with an invalid qualifier.


DEFRULE VLDLQUAL CONTINUE(NEXTRULE)
IF &QUALL NE (SOURCE,CONTROL,COPY,MACRO,MACLIB) THEN ISSUE WRITEMSG(WRNMSG01)
DEFMSG WRNMSG01 "** WARNING ** &DSNAME INVALID"

Note: TSO users: If a TSO allocation request is used to test the sample rule, and no routing parameters have been requested, the TSO TPUT interface is used to write messages. The product does not use the WTO (write-to-programmer) interface because a TSO user can disable delivery with a PROFILE NOWTP command. The TPUT interface ensures that the message is delivered.

Sample message output from a TSO Ready session:


READY
alloc da(don.test) sp(1) tr
** WARNING ** DON.TEST INVALID
READY

Sample message output from an ISPF 3.2 allocate request would result in a clear-screen request followed by the warning message:


** WARNING ** DON.TEST INVALID
***

Batch jobs and started tasks

When the same rule is encountered in a batch job or started task, the default destination for the message is the JES job log (job output). When a user examines the job output, the messages appear among the operating-system allocation messages and step completion codes. The message does not appear on the console or in the system log data set.

Example: the following JCL shows a simple IEFBR14 job with a DD statement that will cause the warning message to be embedded in the job output.


 //DONR   JOB ...
 //STEP1  EXEC PGM=IEFBR14
 //DD1    DD DSN=DON.TEST,
 //        DISP=(NEW,CATLG,DELETE),
 //        DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120,DSORG=PS),
 //        SPACE=(CYL,(1,1))

The job output contains both the warning message and the typical JES or OS messages. Example excerpt of the job output:


** WARNING ** DON.TEST INVALID
IEF236I ALLOC. FOR DONR STEP1
IGD100I 012B ALLOCATED TO DDNAME DD1 DATACLAS ( ) IEF142I DONR STEP1 - STEP WAS EXECUTED - COND CODE 0000
IEF285I DON.TEST CATALOGED
IEF285I VOL SER NOS= STOR04.

IEF373I STEP OR STEP1START 2004233.1056
IEF374I STEP OR STEP1STOP  2004233.1056 CPU0MIN 00.04SEC SRB0MIN 00.00S
IEF375I  JOB OR DONRSTART  2004233.1056
IEF376I  JOB OR DONRSTOP   2004233.1056 CPU0MIN 00.04SEC SRB0MIN 00.00S

Note: IDCAMS: By default, messages written while running under IDCAMS control are added to the SYSPRINT DD statement regardless of the execution environment (TSO, batch, or started task). The test was performed using the ACCVSAM component; the rules issue warning messages before IDCAMS writes records to the SYSPRINT DD statement. Two warning messages may be written—one for the VSAM data component and one for the index.


** WARNING ** DON.TEST INVALID
** WARNING ** DON.TEST INVALID
IDCAMS SYSTEM SERVICES TIME: 16:17:09
DEFINE CLUSTER(NAME(DON.TEST) + 00000060
VOLUME(STOR05) SHAREOPTIONS(2) + 00000070
RECORDSIZE(474 474) CYL(1 1) + 00000092
INDEXED KEYS(1 4)) 00000093
IDC0508I DATA ALLOCATION STATUS FOR VOLUME STOR05 IS 0
IDC0509I INDEX ALLOCATION STATUS FOR VOLUME STOR05 IS 0
IDC0512I NAME GENERATED-(D) DON.TEST.DATA
IDC0512I NAME GENERATED-(I) DON.TEST.INDEX
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0
IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 0

Default message destinations - syncsort_simulate_2000 - Latest

Syncsort™ Storage Management Portal 2000 Rules Language Guide