Beware when you give CP RR access to CF1: CP can have to read files from
there while it is running. The most obvious are the logon LOGO files. If
you change them on the fly while CP has RR access, CP can get the problem we
know as CMS users: 'error 3 reading file'.
*CPLISTFILE * * A STAT*
I load 1st level z/VM system with EXTENT 1. Then log on MAINT user.
Usually we can link cf1 by 'link * cf1 cf1 mr'. But our system response
following message to this command:
HCPLNM101E DASD 0CF1 forced R/O; R/O by SYSTEM; stable by SYSTEM
Why SYSTEM catch it?
Best Regards!
Gao Lu (高路)
I/T
@LISTSERV.UARK.EDU
Subject: CF1 can not linked as MR
I load 1st level z/VM system with EXTENT 1. Then log on MAINT user.
Usually we can link cf1 by 'link * cf1 cf1 mr'. But our system response
following message to this command:
HCPLNM101E DASD 0CF1 forced R/O; R/O by SYSTEM; stable by SYSTEM
Why SYSTEM catch
Gao,
Your SYSTEM CONFIG (on the MAINT 0CF1) probably contains:
CP_Access MAINTCF1 A
Normally you want to issue CPREL A before you update the parm disk,
followed by a CPACC MAINT 0CF1 A to reaccess it again.
But you can also change the SYSTEM CONFIG line into:
CP_Access MAINTCF1 A RR
