Re: DMKLOG052E ERROR IN CP DIRECTORY

On 8/27/2010 10:05 PM, Mike Stramba wrote:
>
> DCP seems to only take a hex arg, how would you locate the operator VMBLOK ?

CP LOCATE <userid>
Or.. for the adventurous
Chase the VMCBLOK Q shaped VMBLOK CHAIN (SYSTEM is found in PSA's ASYSVM 
offset, The Next VMBLOK (VMQFPNT in the VMBLOK) is the CP operator (not 
necesserally the OPERATOR USER) and next VMQFPNT points to the next 
user.. Last in the chain points back to the CP OP VMBLOK (not SYSTEM 
VMBLOK - Hence Q shaped).

NOTE : In VM/370 terms, The CP operator is the 1st Class A user to log 
on. After an IPL that's going to be the OPERATOR user, but it may change 
along the way. The CP operator also has specifics :

- All CP messages are timestamped
- Default TERM is TERM MODE CP instead of TERM MODE VM

>
>>> - "link *<mdisk>  <vcuu>  RR" (because you can link to your own minidisk without needing a password) - where<mdisk>  is the minidisk holding the CP directory and vcuu is any virtual address..
>
> Hmm, who owns the 231 disk ? ..   a  LINK  maint 231 231 rr read gives
> : 231 not linked no read password

When you are a linking to your OWN minidisks, you should use the syntax:
CP LINK * <cuu> <cuu> <mode>
Specifying '*' as the user as a specific meaning for the link command.

>
> "ACC<vcuu>  <letter>" and then "DIRECT<dirname>  DIRECT<letter>"..
> This will ensure the directory is properly written AND that the
> allocation table holds the proper flag for the area containing the
> "Active Directory".)
>

This or the "Six Pack" is even more warped than I thought..

--Ivan