ASAP 3.2 Messages Manual

HP NonStop Messages Manual Page 97 of 414
Recovery. ASAPX ignores all non-SET commands in the ASAPXCNF file. To
eliminate this warning message, remove the non-SET commands from the file.
1861
Resetting file security: fname
Cause. ASAPX found that the security on a segment file fname was incorrect. This
message is a warning that the ASAPXMON is going to stop. Restart it to properly reset
the file’s security.
Effect. ASAPXMON will stop and restart to secure the segment file properly.
Recovery. ASAPX automatically corrects the security problem. To eliminate this
warning message, change the default NonStop Kernel security string for the user ID
that starts ASAP to AAnn.
1862
No SET NAMEFILE command found in: fname
Cause. (ASAP Release 1 only) ASAPX did not find a SET NAMEFILE command in
the ASAPXCNF fname file. This could result in reserved names being entered as
domain names and could yield unexpected results in ASAP, OEM, and OIL.
Effect. ASAPX is not affected; however, using reserved names as domain names can
cause a myriad of problems in ASAP, OEM, and OIL.
Recovery. ASAPX warns about this problem and continues processing normally. To
eliminate this warning message, add a SET NAMEFILE $ISV
Volume.ZASAPX.ZASPXNAM command to ASAPXCNF.
1863
EDITREAD error on NAMEFILE: fname, Er: error
Cause. (ASAP Release 1 only) ASAPX encountered an EDITREAD or
EDITREADINIT error while processing the ASAP reserved names file fname. This
could result in reserved names being entered as domain names and could yield
unexpected results in ASAP, OEM, and OIL.
Effect. ASAPX is not affected; however, using reserved names as domain names can
cause a myriad of problems in ASAP, OEM, and OIL.
Recovery. ASAPX warns about this problem and continues processing normally. To
eliminate this warning message, correct the problem indicated by the EDITREAD error
number; then restart ASAPX.