Hi Dave,

Is that read-only link to the 540RES defined as VMACCT’s 1A0?  

 

Is there a DIRECT 1A0 record in the VMACCT CONFIG file on it’s 191 disk that 
has the correct volume label? 

 

Does the link cover the full pack including cylinder 0? This is where we see 
the most problems in this area. VM:Account requires that link to cover the full 
pack including cylinder 0. It requires access to the volume allocation map so 
knows where the object directory resides on that volume.

 

 What abend occurs?

 

That link will show as z/OS formatted so that is normal.  VMACCT just requires 
the R/O link to the full volume definition, it shouldn’t be accessed.

 

If none of the above information helps, please call  CA support for the VM 
products so we can help you out.

                Regards,

                                Yvonne

 

Yvonne DeMeritt 
CA 
Senior Sustaining Software Engineer 
 

From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf 
Of Dave Keeton
Sent: Monday, November 16, 2009 4:29 PM
To: [email protected]
Subject: VM:Account & MAINT's 123 disk

 

I am attempting to install CA:Account and I have been unable to get it to start 
properly (it abends) because it isn't reading the object directory. I have 
defined a read-only link to MAINT's 123 disk (540RES) where the user directory 
is located, but it appears as OS formatted and not CMS to the VMACCT machine. 
I've tried linking instead to DirMaint's 123 link and got the same result. I'm 
not sure I understand why it's appearing that way and how to present it to 
VMACCT so it can read the user directory.

Thanks in advance,

Dave

Reply via email to