

Special Monitoring Situations › Special Monitoring Situations › Segmented Monitoring to Handle Special Situations › Location Restrictions
Location Restrictions
The following bullets list location restrictions:
- Regardless of how they are set (Source Listing, Menu, or single‑line command); each of these options must be placed on the first byte (the op‑code) of a machine instruction that resides in non‑store‑protected virtual storage. Because the code must not be store‑protected, the application programs must not reside in the LPA, ELPA, or ERDSA.
- Regardless of how they are set (Source Listing, Menu, or single‑line command); each of these options must be placed on the first byte (the op‑code) of a machine instruction that resides in non‑store‑protected virtual storage. Because the code must not be store‑protected, the application programs must not reside in the LPA, ELPA, or ERDSA.
- Any piece of code with these options must remain resident at the same virtual storage address until the options are removed.
- These options cannot be placed on sequential statement numbers or instruction addresses; that is, these options must be separated by at least one machine instruction.
- In Command Level CICS applications within code generated by an EXEC CICS, these options must not be placed on the LOAD 15 that precedes the BALR 14,15 or on that BALR.
Copyright © 2014 CA Technologies.
All rights reserved.
 
|
|