Assembling and linking netView/390 exits - ironstream_for_servicenow_event_mgmt - 7.4

To run in the NetView/390 address space, Ironstream uses three exits, a DST, and a command processor.

Modify and submit the JCL in hlq.SAMP(ASMJCL) according to instructions in that member to create one or more of the following load modules, based on your needs:

Load Module Name Description NTIPPI This program runs as a NetView DST task. It collects the messages, alerts, and command responses from the other four programs and sends it out of the NetView address space, via the SSI, to the VP390 address space. This program must be assembled and running if any of the other four programs below are to be used. DSIEX06 This exit captures solicited VTAM message responses from commands that NetView operators issued through the NetView Primary Operator Interface (POI). Use this exit if you expect NetView operators to be issuing VTAM Vary commands against SNA resources, and you want ServiceNow to see the effects of such commands on the SNA network. DSIEX11 This exit captures unsolicited VTAM messages that come in through the NetView POI. DSIEX11 is generally more important than DSIEX06, since DSIEX06 messages are user-initiated, while DSIEX11 messages will be generated unexpectedly when there is trouble in the SNA network. NTIMQS This program is used by CLISTs running under a NetView autotask. The CLISTs execute NetView commands sent to the mainframe from the MID server, either automatic actions or individual operator commands, so by restricting the command security level of the NetView autotask, you can restrict what NetView commands may be executed from the MID server. When the command responses arrive, the CLIST will use this NTIMQS program to forward the response message(s) to the NTIPPI task.