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.

CVTOVRID<br />

CVTOVRID<br />

►►<br />

CVTOVRID<br />

Authorization<br />

Purpose<br />

Oper<strong>and</strong>s<br />

Usage Notes<br />

OVERRIDE<br />

fn<br />

CONFIG<br />

Privilege Class: Any<br />

1794 z/<strong>VM</strong>: <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> <strong>and</strong> <strong>Utilities</strong> <strong>Reference</strong><br />

ft<br />

fm<br />

A1<br />

Use the CVTOVRID sample utility program to convert a CMS class override file<br />

(one that is processed by the <strong>CP</strong> OVERRIDE utility) into a series of MODIFY<br />

statements to imbed into a system configuration file.<br />

Note: CVTOVRID is an XEDIT MACRO, so you must be editing (XEDITing) the file<br />

that you want to convert when you invoke this utility.<br />

fn is the file name of the output file that will contain the MODIFY configuration file<br />

statements. If omitted, the default file name is OVERRIDE.<br />

ft is the file type of the output file that will contain the MODIFY configuration file<br />

statements. If omitted, the default file type is CONFIG.<br />

fm is the file mode of the output file that will contain the MODIFY configuration file<br />

statements. You must have a link that allows you to write to the disk (or SFS<br />

directory) accessed at the specified file mode. If omitted, the default file mode is<br />

A1.<br />

1. After creating the file of MODIFY statements, you must:<br />

a. Add an IMBED statement to your system configuration file to pull in the new<br />

file (or move the MODIFY statements from the new file to your system<br />

configuration file)<br />

b. Make sure that the new file (or your system configuration file) is on the parm<br />

disk.<br />

2. <strong>CP</strong> maintains some of the QUERY subcomm<strong>and</strong> control blocks off of a virtual<br />

subcomm<strong>and</strong> chain. These blocks are for QUERY VIRTUAL subcomm<strong>and</strong>s <strong>and</strong><br />

generic subcomm<strong>and</strong>s for which there is no specific oper<strong>and</strong> that identifies<br />

them. For example, QUERY 0003 for a class B user is identified by the generic<br />

QUERY subcomm<strong>and</strong> block because the second oper<strong>and</strong>, which would be used<br />

to identify it, is a device address of which there is no single keyword that<br />

indicates that a real device is being queried. If no keyword is found, then the<br />

entry point for the generic QUERY subcomm<strong>and</strong> is used, provided that the user<br />

has the correct privilege class.<br />

►◄

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

Saved successfully!

Ooh no, something went wrong!