Is SASSXDSN (external data set tracking table) used in tracking external file creations on distributed servers?

Products

• CA 7 Workload Automation

Issue/Introduction

Is SASSXDSN (external data set tracking table) used in tracking external file creations on distributed servers?

 

 

Environment

Release:
Component: 7

Resolution

SASSXDSN is not used for tracking external files on distributed servers.

If you are using XEVENTS via the TRACKER to track file creations on the distributed servers, you do not need to define the file or dataset to SASSXDSN (external file tracking table). SASSXDSN is used only for tracking data sets created or updated on the mainframe.

The TRACKER uses the XEVENTS to send a request to the distributed system running UUJMA or CA AUTOSYS to track file creations. UUJMA or CA Autosys will notify the TRACKER of a file creation or update and the TRACKER will cut a pseudo SMF type 15 record that will be processed by ICOM and passed on to CA 7.

The following is an example of a XEVENTS rule to track a file on windows server that is running UUJMA:

EVENT( NODE(WIN06w) -                

TYPE(DSN) NAME(c:\test\your.test_file) -

JNO(0001) mvsname(YOUR.TEST.FILE.COMPLETE) )

In the above example, when payroll_file is create on windows server WIN06W, UUJMA will send the TRACKER a DSLCOSU record. The TRACKER will match the file name against an internal table and create a pseudo SMF type 15 record based upon the MVSNAME specified. In this example the pseudo SMF type 15 record will be for data set YOUR.TEST.FILE.COMPLETE.  ICOM will pick up the SMF type 15 record and write it out to the Communications Data Set (UCC7CMDS DD) and CA 7 will process this record as it does any other SMF records written by ICOM.