Cross-Platform Tracking Examples and Usage Notes

This article details cross-platform tracking usage notes and examples.
ca712
This article details cross-platform tracking usage notes and examples.

XEVENTS Example 1

When file c:\dir\myfile.txt is created or updated on node NTBOX1, XTRK tracks the creation/update of data set name NTBOX1.MYFILE.TXT as a 
CA 7
 external data set.
  EVENT( TYPE(DSN) -          NODE(NTBOX1) -          NAME(c:\dir\myfile.txt) -          MVSNAME(NTBOX1.MYFILE.TXT)  )

XEVENTS Example 2

The other
Broadcom
scheduler or agent sends XTRK feedback when job 'payjob-on-unix', job number '0001' in jobset 'payroll-jobset-on-unix' initiates and terminates at node UNIX01. XTRK tracks it as a 
CA 7
 external job with the name UNIXPAY1.
  EVENT( TYPE(JOB)      -          NODE(UNIX01)   -          NAME(payjob-on-unix)  -          JNO(0001)      -          JOBSET(payroll-jobset-on-unix) -          MVSNAME(UNIXPAY1)  )

XEVENTS Example 3

Each
Broadcom
scheduler or agent that XTRK connects with, whose CAICCI node name begins with the characters 'AIX', is asked to send XTRK feedback when job 'aix-job1', job number '0001' in jobset 'aix-jobset' initiates and terminates. XTRK tracks it as a 
CA 7
 external job with the name AIXJOB1. This definition lets you set up one rule that captures tracking for this job regardless of which AIX computer it runs on.
  EVENT( TYPE(JOB)      -          NODE(AIX*)     -          NAME(aix-job1)  -          JNO(0001)      -          JOBSET(aix-jobset) -          MVSNAME(AIXJOB1)  )

XEVENTS Example 4

These rules ensure that XTRK attempts to communicate with each of these systems (AIX001, AIX002, AIX003). Typically, XTRK communication only occurs if
CA 7
submits a cross-platform job to that remote system. If you simply want to listen for cross-platform external tracking events at a node, the TYPE(CONNECT) rule esnures that XTRK attempts to establish communication with that system.
  EVENT( TYPE(CONNECT) NODE(AIX001) )   EVENT( TYPE(CONNECT) NODE(AIX002) )   EVENT( TYPE(CONNECT) NODE(AIX003) )

Cross-Platform Usage Notes

Duplicate External Events
If you are running
CA 7
Cross-Platform Tracking System (XTRK) on more than one MVS image, do not use the same XEVENTS rules for both copies. If you do, each XTRK could receive feedback for the same remote job or file event. Depending on the timing of XTRK, ICOM, and
CA 7
processing, this situation could result in either of the following outcomes:
  • Duplicate triggers (at worst).
  • Unnecessary overhead in the
    CA 7
    address space (at best).
We recommend having one copy of XTRK handle the Cross-Platform External Tracking for
CA 7
.
Using TYPE(CONNECT) Event Rules
Typically the
CA 7
Cross-Platform Tracking System (XTRK) only communicates with those remote systems where
CA 7
Cross-Platform jobs are submitted to. To use XTRK for remote systems that do not receive any
CA 7
cross-platform work, define at least one XEVENTS rule that explicitly references that node. If the only rules that apply to that node have generic NODE( parameters, use a TYPE(CONNECT) rule to identify explicitly the node to XTRK.
SASSEXTT Model Queue Record Table Module
For
CA 7
to track external tasks (local or cross-platform), the Model Queue Record Table module, SASSEXTT, must be available to the
CA 7
address space. The External Job/STC Filter Table module, SASSEXTL, is
not
required for cross-platform external tracking.
For more information about tracking external tasks, see the External Tracking and Filtering topic.