Share JES2 exit points

All ThruPut Manager exit routines invoke subsequent exit routines at the same exit point. However, for exits 8, 14, and 49 see Sharing JES2 Exit 8and Sharing Exit 14 and Exit 49.

Return codes from BMC ThruPut Manager JES2 exits

Many of the standard exit points in JES2 allow return codes that preempt calls to subsequent exits taken at the same entry point. The following tables describe the codes returned by ThruPut Manager JES2 exits. Use these tables with the list or return codes for the specific exit (as documented in the JES2 Initialization & Tuning Guide) to make sure that your installation’s exits still work correctly in a BMC ThruPut Manager environment. Where the return code is non-zero, another exit is not called.

DTMOMX05—JES2 exit 5
0	Command was not a BMC ThruPut Manager command. No action is taken.
4	Not used
8	Internal BMC ThruPut Manager interface command. Processing was successful.
12	Message returned by BMC ThruPut Manager is displayed

DTMOMX07—JES2 exit 7
0	Always returned
All others	Not used

DTMOMX08—JES2 exit 8
0	Always returned
All others	Not normally used

DTMOMX10—JES2 exit 10
0	No action is taken.
4	Not used
8	BMC ThruPut Manager has suppressed the message.

DTMOMX14—JES2 exit 14
0	BMC ThruPut Manager has determined that this is not a request to select a job for execution.
4	Not used
8	A job has been selected for execution.
12	No jobs are eligible to be selected.

DTMOMX19—JES2 exit 19
0	Initialization statement is not a BMC ThruPut Manager initialization statement.
8	TMPARM initialization statement processed.
All others	Not used

DTMOMX24—JES2 exit 24
0	BMC ThruPut Manager environment analyzed and found to be correct.
All others	Not used

DTMOMX49—JES2 exit 49
0	Always returned. If the flag X049SKIP in the byte X049RESP is set to B’1’, the job has been skipped.
All others	Not used

JES2 Job Exit Mask

The JES2 Job Exit Mask associated with each job is located in the field JOBMASK in the JCT. The Job Exit Mask can cause certain job-related exits to be bypassed. BMC ThruPut Manager is sensitive to changes involving JES2 exits 7 and 8, so make sure that any manipulation of the Job Exit Mask does not prevent the BMC ThruPut Manager exit routines from being called.

Sharing JES2 exit 8

JES2 exit 8 (HASPSSSM JCT Read/Write) is invoked in the user’s address space during the Job Analysis and again during normal job run. Depending on the purpose and logic of your installation exit 8 routine, this might be undesirable. The JES2 exit 8 routine is designed so that you can eliminate calls to exit 8 during the Job Analysis phase.

To prevent calls to other exit 8 routines, you can change the source module for DTMJ2SV8 supplied with ThruPut Manager so that return codes are passed to other exits based on the processing decisions made by ThruPut Manager’s use of exit 8.

BMC ThruPut Manager exit 8 returns via a return code routine. This routine is shipped in source form. It contains a mapping table that maps the return codes from exit 8 to the return code routine and the corresponding return to your routines.

The table maps all return codes to 0 so your routines are always called. You can modify this mapping to influence the subsequent calling of your routines.

The following table shows the relationship between the codes returned by exit 8 to the source stub and the actual return codes returned at the completion of exit 8. (This represents the way BMC ThruPut Manager is delivered to you.) The completion return codes are the ones that affect your routines.

To stub	To your routines	Action
Code	Completion code
0	0	The exit took no action since the job was not eligible for BMC ThruPut Manager processing.
non-zero	0	Job was processed by Job Analyzer.

Sharing Exit 14 and Exit 49

Sharing exits 14 and 49, the Job Queue Work Select QGET exits, can be shared without concern with one exception. If the purpose of the exit is to select jobs for execution, might conflict with the BMC ThruPut Manager use of the exit. In this case, contact BMC Support.