NRJETrace

An eight-character input byte array. The Wsid parameter identifies your workstation. It must contain a left-justified alphanumeric name beginning with a letter. If the workstation identifier is less than eight characters long, it must be followed by blanks.

An input integer. The TraceOnOff parameter indicates whether to initiate or terminate the tracing specified in Traces. Values are as follows:

A two-element input integer array. Each element of Traces contains an integer that represents a type of tracing to turn on or off.

The use of two elements allows you to enable multiple trace types simultaneously. The order of entry of the elements is not significant. Traces element values are as follows:

Following is an example of Traces for LU tracing only:

1
0

An input integer. The TraceFileLen parameter is the length in characters of the trace file designator, TraceFile.

The number of characters may be between one and thirty-five. If this parameter is zero, the trace is recorded in the DefaultFile.

An input integer. TraceMedium indicates the TraceFile device type. This parameter is called by reference. The only valid value for TraceMedium is 0, which indicates that the trace information will be written to a disk file.

An input single-word integer. TraceSize contains the maximum number of logical records TraceFile is to contain, from 0 through 32767.

A logical record is 128 words long. If TraceSize is zero, the default size of 1024 records is used.

An input byte array. The TraceFile byte array contains an actual file designator used for trace output. This parameter is used only when TraceFileLen is greater than zero. This parameter identifies a disk trace output file. TraceFile can contain a fully qualified 35-character disk file name, with lockword, in this form:

     filename[lockword][groupname[acctname]]

The contents of TraceFile must be left-justified, with trailing blanks, and meet MPE standards for an actual file designator.

If you specify a disk file that does not exist (a NEW file), then it will be created as the destination for trace output.

If you specify an OLD file (it already exists), and it already is in use for trace output, then trace output records for this activity are interleaved with other trace output records. You minimize the use of disk space by using an OLD file appropriately; however, trace output can be overwritten. If you specify an OLD file that is not already open, the file will be overwritten with new trace data. No warning is issued. Trace file records are created after successful completion of the intrinsic. If an error is encountered during the execution of the intrinsic, only the status array will be traced.

An output byte array. The DefaultFile parameter is the file designator of the default trace file. A default file name is created whenever TraceFileLen is zero.

Default file names are in the form NMTCnnnn.PUB.SYS, where nnnn is a four-digit number that is incremented each time a default trace is created. Default file names are up to 27 bytes long. The last character is always a blank. You can always retain trace data by using a DefaultFile; however, considerable disk space might be used.

An eight-element integer output array (required). The Result array contains error codes that occurred during execution of this intrinsic.

The first element of the Result array is set to zero if no errors took place. The structure of the Result array is described in "Parameters Common to NRJE Intrinsics" in the introduction to Chapter 5 “User Intrinsics”

Always test the first element of Result immediately after you call this intrinsic. If the first element of Result is not zero, test the other elements of Result to determine the nature of the problem that has occurred.