It may be that there are commands that can be used that do not require
displaying host storage. What are you trying to accomplish? If you are
looking for total and remaining space available, for instance, the
response to QUERY ALLOC may be all that is needed. 

q alloc spool                                                   
                EXTENT     EXTENT  TOTAL  PAGES   HIGH    %     
VOLID  RDEV      START        END  PAGES IN USE   PAGE USED     
------ ---- ---------- ---------- ------ ------ ------ ----     
VW3SP1 C890          0       3338 601020 223852 504209  37%     
VW3SP2 C058          0       3338 601020 251332 493942  41%     
VW3SP3 C167          0       3338 601020 180079 407992  29%     
V3SP04 CCFE          1       3338 600840 232100 576202  38%     
V3SP05 B83B          1       3338 600840 298477 491040  49%     
V3SP06 CE1D          1       3338 600840 286382 548100  47%     
V3SP07 B843          1       3338 600840 294841 597423  49%     
V3SP08 B890          1       3338 600840 281302 600840  46%     
V3SP09 B845          1       3338 600840 287700 600551  47%     
VMDMPA B858          1       3338 600840 517187 517187  86% DUMP
VMDMPB DC63          0      10016  1761K     12     12   1% DUMP
                                  ------ ------        ----     
SUMMARY                            7629K  2786K         36%     
USABLE                             5281K  2281K         43%  

This can be processed by a pipe or if detailed information is desired,
or  if all you want is to know totals, 

   parse value diag(8,'Q ALLOC SPOOL') with 'USABLE' tot inuse .

gives the values. 

You get similar results for Q ALLOC PAGE or TDISK. 

I have used host storage displays in the past but have found them to
sometimes be problematic when migrating to new releases, while the
documented command responses tend to be more change resistant and,
therefore, make it easier to maintain the EXECs.  

Regards, 
Richard Schuh 


-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Imler, Steven J
Sent: Friday, March 30, 2007 12:09 PM
To: [email protected]
Subject: Re: Exec errors

Alyce,

The HOST storage display under z/VM 5.n have an "HL" prefix:

<<< snip >>>
d h20000.20
HL00020000  00000000 00000000 00000000 00000000 04 R00020000
<<< snip >>>

In previous releases, the prefix was only "H" ... I'm sure the "L" is
what's causing your EXEC to fail in this case.

JR

JR (Steven) Imler
CA
Senior Software Engineer
Tel:  +1 703 708 3479
Fax:  +1 703 708 3267
[EMAIL PROTECTED]
 

-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Alyce Austin
Sent: Friday, March 30, 2007 02:32 PM
To: [email protected]
Subject: Exec errors

Hello,

I'm trying to run some execs to check spool, rdr and print files
on my test z/VM 5.2 system and this is what I get:
















SPOOL CONS * START

CHECKPRT
    11 +++ SPAV = X2D(SUBSTR(DIAG(8,'DISPLAY H'D2X(PGDSP+AV)),12,8))
DMSREX475E ERROR 40 RUNNING CHECKPRT EXEC, LINE 11: INCORRECT CALL TO
ROUTINE
READY(20040); T=0.01/0.01 10:39:19
CHECKSP
    10 +++ PGAV = X2D(SUBSTR(DIAG(8,'DISPLAY H'D2X(PGDPG+AV)),12,8))
DMSREX475E ERROR 40 RUNNING CHECKSP EXEC, LINE 10: INCORRECT CALL TO
ROUTINE
READY(20040); T=0.01/0.01 10:39:22
CHECKRDR
    11 +++ SPAV = X2D(SUBSTR(DIAG(8,'DISPLAY H'D2X(PGDSP+AV)),12,8))
DMSREX475E ERROR 40 RUNNING CHECKRDR EXEC, LINE 11: INCORRECT CALL TO
ROUTINE
READY(20040); T=0.01/0.01 10:39:25


They work fine on my z/VM 4.4 production system.

Any ideas what I need to change to get them to
work on z/VM 5.2?

Thank for your help,
Alyce

Reply via email to