Invoking the Service

The following information describes the environment required, restrictions, register information, performance implications, and abend codes for the file copy notification service.

Environment

Minimum authorization:
Problem state or supervisor state, and any PSW key. The caller does not need to be APF-authorized.
Dispatchable unit mode:
Task
Cross memory mode:
PASN=HASN=SASN
AMODE:
31–bit
ACS mode:
Primary
Interrupt status:
Enabled for I/O and external interrupts
Locks:
No locks can be held
Control parameters
Control parameters must be in the primary address space

Programming requirements

  • The CICS® VR file copy notification service can be started by the high-level languages supported by Language Environment® and by assembler language callers.
  • For assistance when coding the CICS® VR file copy notification service in assembler language, CICS VR provides the caller with a sample DWWIFCNS which is located in the SDWWSORC library with the non-server related reason code equates.
  • The caller of the CICS® VR file copy notification service can have an established FRR.
  • The CICS® VR file copy notification service can be started in one of the following ways:
    • A CALL statement is coded in the invoking application. The invoking application is link-edited with the notification service module DWWCVRN in the library SDWWCSSL.
    • The invoking application can issue a LINK or LOAD/CALL to the CICS VR file copy notification service. This technique ensures that your program always has the latest copy of the service. The library (SDWWCSSL) that contains the file copy notification service must be in the Link List or referenced by JOBLIB, STEPLIB, or the task library of the invoking application.
    Note:
    The sample describes calling the CICS® VR file copy notification service from a reentrant program written in assembler language. See z/OS® MVS™ Programming: Assembler Services Reference, Volume 1 (ABEND-HSPSERV) for information about using the CALL macro. For information about using CALL in programs written in high-level languages, see the applicable language document.

Restrictions

The CICS® VR server address space must be active on the system that requests the CICS® VR file copy notification service.

Input register information

Before using the service, the caller does not have to place any information into any register unless using it in register notation for a particular parameter, or using it as a base register.

Output register information

When control returns to the caller, the general purpose registers (GPRs) contain:
Register Contents
0 Reason code
15 Return code

Some callers depend on register contents remaining the same before and after issuing a service. If the system changes the contents of a register on which the caller depends, the caller must save them before issuing the service, and restore them after the system returns control.

Performance implications

None.

Abend Codes

Callers of the CICS® VR file copy notification service might encounter the following ABEND codes:
ABEND CODE Meaning
0C4 The system cannot properly access a user-provided parameter
B78 The caller was not enabled for I/O and external interrupts.
80A Insufficient storage available for the service.