27.12.2012 Views

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Response 2:<br />

To display the current information for <strong>CP</strong> exit point X'D5', enter the following:<br />

query exits d5<br />

Exit Status Calls Returns Seconds<br />

00D5 Enabled 8 8 10.008833<br />

EPNAME Attempts Calls Seconds<br />

H<strong>CP</strong>SRC00 8 8 0.002598<br />

H<strong>CP</strong>SRCZZ 8 0 0.000000<br />

H<strong>CP</strong>SRC08 8 4 0.002833<br />

H<strong>CP</strong>SRC99 6 6 10.002668<br />

Ready;<br />

In this example, the first 2 lines show that <strong>CP</strong>:<br />

v Is accepting requests to process this exit point.<br />

v Entered <strong>and</strong> exited this exit point 8 times, which means the exit point is not<br />

currently active.<br />

v Used a little more than 10 seconds to set up this exit point <strong>and</strong> process all calls<br />

to all its entry points.<br />

The remaining lines show that:<br />

v Exit point X'D5' currently has 4 entry points (H<strong>CP</strong>SRC00, H<strong>CP</strong>SRCZZ,<br />

H<strong>CP</strong>SRC08, <strong>and</strong> H<strong>CP</strong>SRC99).<br />

v <strong>CP</strong> tried to call H<strong>CP</strong>SRC00 8 times <strong>and</strong> succeeded in each case.<br />

v <strong>CP</strong> tried to call H<strong>CP</strong>SRCZZ 8 times, but none of the attempts were successful.<br />

(This probably means that someone did not load H<strong>CP</strong>SRCZZ yet.)<br />

v <strong>CP</strong> tried to call H<strong>CP</strong>SRC08 8 times. Only 4 of those attempts were successful.<br />

(This can happen when someone loads an entry point after associating it with an<br />

exit point.)<br />

v <strong>CP</strong> tried to call H<strong>CP</strong>SRC99 6 times <strong>and</strong> succeeded in each case. However, there<br />

are 2 odd things about H<strong>CP</strong>SRC99:<br />

1. <strong>CP</strong> called the other entry points 8 times, but only called H<strong>CP</strong>SRC99 6 times.<br />

(This probably means that someone associated the entry point with the exit<br />

point sometime after the other 3 entry points.)<br />

2. The elapsed time to process H<strong>CP</strong>SRC99 is substantially longer than that of<br />

the other 3 entry points. (Unless this entry point is substantially larger than<br />

the others, this probably means someone should investigate this entry point.)<br />

Response 3:<br />

To display the current information for <strong>CP</strong> exit point X'1234', enter the following:<br />

query exits 1234<br />

Exit Status Calls Returns Seconds<br />

1234 Enabled 3 3 0.000803<br />

Location Instruction Resolution<br />

H<strong>CP</strong>XMGMS+0004 41700000 RESOLVE<br />

Defined by: OPERATOR at 13:27:54 on 09/03/98<br />

PARM R9<br />

RC<br />

EPNAME Attempts Calls Seconds<br />

EXITSTDP<br />

Ready;<br />

3 3 0.000785<br />

In this example, the first 2 lines show that <strong>CP</strong>:<br />

v Is accepting requests to process this exit point.<br />

QUERY EXITS<br />

Chapter 2. <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> 793

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!