with Tags:
command
X
X
How to get z/VSE debug data
If you have problem with your z/VSE system (such as a system hang, soft- or hardwait) and contact the z/VSE Service (Level 2) Team, you are often asked to run a debug trace and try to reproduce the problem. The debug trace area is allocated in the Shared Virtual Getvis Area (31 bit). If the problem reoccurs, z/VSE Level 2 asks to send a standalone or system (AR) dump, which includes the debug trace area. Debug traces system events and records registers and control data. With that information you or the Level 2 team may get closer to the cause... [More]
Tags: console supervisor command attention_routine debug trace service vse ar documentation |
Quiesce / shutdown signal in z/VSE
Are you aware of the signal quiesce / shutdown support in z/VSE ? This support is available since z/VSE Version 4. z/VSE doesn't have a controlled shutdown process, but you may implement that e.g. with REXX procedures to your needs und use the quiesce support to trigger the shutdown. The signal quiesce support can be used to inform a z/VSE image, that shutdown is requested. See more details below: To configure z/VSE for signal quiesce, you use the QUIESCE parameter of the IPL SYS control statement. If a disruptive operation (for example, an... [More]
Tags: signal vm command quiesce shutdown vse iml |
z/VSE Console commands: LOCATE and SHOW
Today I have two Attention Routine (console) commands that may be useful - LOCATE and SHOW. These commands are described in the z/VSE Supervisor Diagnosis Reference Manual (DRM). The Supervisor DRM provides insight into the z/VSE architecture. You can download DRMs from here . LOCATE command: The LOCATE command scans the virtual storage for the next occurrence of either a character-, or a hexadecimal-character string whereby parts of the string may be unknown. The total string is limited to 16 characters or 32-hex digits. SHOW command: The... [More]
Tags: show attention_routine console locate vse ar command |
How to stop long running re-display ?
Today I have a tip related to z/VSE's console support. On the console you may use PF7 (RED) to re-display earlier messages. It is also possible to specify a filter on the VSE command line, before you press PF7 - such as the partition id (BG, F1, ...) or IPL (to display the IPL messages). z/VSE messages are written to the VSE hardcopy file. If you re-display messages, they are retrieved from the VSE hardcopy file. Sometimes, when you are searching through the VSE Hardcopy File (by specifying a filter before pressing PF7), it may happen that... [More]
Tags: vse tips hints command console technical |
How to measure z/VSE I/O performance ?
There are several ways to measure the I/O performance of your z/VSE workload. The best tools are provided by performance monitor products from z/VSE vendors. Just for getting some information about the I/O behavior of your system, you may use the SIR command. With the SIR console (Attention Routine = AR) command you can get some characteristics of your workload, such as z/VSE supervisor call usage (SIR MON command) and I/O data. You can retrieve I/O data with the SIR SMF command. The data comes from the Subsystem... [More]
Tags: vse command sir smf io performance |
z/VSE STATUS command
Last week there was a question related to the the z/VSE STATUS command on VSE-L. STATUS is an Attention Routine command. The output is displayed on the console. It provides the status of z/VSE partitions and tasks, addresses of control areas, device status, etc. The STATUS command is described in the z/VSE System Control Statements. Some tips are in the z/VSE Hints & Tips book. For experts: If you want to get more information about the displayed status and internal processes, you can look into the z/VSE Supervisor... [More]
Tags: documentation hints book tips command vse ar knowledge_center status |
How to retrieve information about your z/VSE system
The SIR Attention Routine (console) command provides important information about your system. Just use the SIR with out a parameter or SIR SYS to display the following information on the console: (VM) CPUID and VSE CPUID - CPUID composed of the CPU Identification Number along with the Version Code followed by the Model Number your native system is running on. VSE CPUID shows the virtual CPUID, if the z/VSE system is running in a z/VM guest. PROCESSOR= processor type and serial number LPAR= No= LPAR... [More]
Tags: information service sir vse command service_level |
