Re: DMKLOG052E ERROR IN CP DIRECTORY

"paoloG" <[email protected]>
Newsgroups gmane.comp.emulators.hercules390.vm
Message-ID <[email protected]>




--- In [email protected], Mike Stramba <mikestramba@...> wrote:
>
> > Locate the operator VMBLOK, change the user id to MAINT in real storage (DCP & STCP are your friends there)
> 
> Is the reason for changing the real storage ID to MAINT,  just to get
> access to the DIRECT command (that apparently OPERATOR doesn't have
> access to ?)
> 
> i.e. does changing that STORAGE ID, change the logged in user machine ID ?
> 
Usually SIXPACK DIRECT (the plain text directory) resides on MAINT 191 minidisk (accessed by CMS as 'A' disk).

The DIRECT SIXPACK command reads the file SIXPACK DIRECT; it finds the famous statement: DIRECTORY 231 3350 VM50-1 that means: write the directory on DASD  VM50-1 at address 231.

The location where DIRECT writes the directory on VM50-1 is specified in a map in VM50-1 DASD that was created by a FORMAT/ALLOCATE program.

In MAINT userid there's a statement: MDISK    231 3350 000 555 VM50-1 MW that defines as a fullpack minidisk the VM system disk VM50-1;
so DIRECT command has access to this disk at virtual address 231.

In order to write the directory from user OPERATOR you must:
1) IPL CMS (command DIRECT resides on MAINT 190 accessed as 'S' disk)
2) Have a link to MAINT 191 where SIXPACK DIRECT resides
3) Have a link to MAINT 231 where directory should be written.  

When you issued from MAINT the command 'ACC 231 Q' you tried to access with CMS the system VM DASD VM50-1 (and not the DIRECTORY as you thought).

BFN

Paul
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.