Generic Data Set Interface Guidelines

Consider the following guidelines before using the generic data set interface:

A CA OPS/MVS security event occurs every time a subsystem data set directed to CA OPS/MVS is opened. You can write a security rule to allow or disallow the opening of the data set.
Started tasks, batch programs, or TSO programs can use the generic data set interface.
The CA OPS/MVS subsystem specified as ssid must be active when the job or started task is started.
The application writing to the data set must use either standard QSAM or BSAM.
There are three possible techniques for selecting message IDs from each file:
- If you do not specify the posmsgid parameter, the application must place a message ID as the first token of each record. This token can contain from one to ten characters.
- If you do specify the posmsgid parameter and it is a non-negative numeric value, CA OPS/MVS begins scanning the message ID at or immediately following that position in each record.
- If neither of the above techniques is practical, you can assign a unique one to eight character non-numeric MSGID for all records from the file in the posmsgid parameter. For examples of each of these three techniques, see the previous section.
Messages exceeding 128 characters are truncated.
If CA OPS/MVS terminates, generic data set interface messages are no longer automated. If you restart CA OPS/MVS, the messages will again be sent to the AOF. You do not need to stop and restart the application if you use the same CA OPS/MVS subsystem ID when restarting CA OPS/MVS.