ELowell: /* Overview */

2017-10-26T17:15:07Z

Overview

← Older revision		Revision as of 17:15, 26 October 2017
Line 3:		Line 3:
	==Overview==		==Overview==
	<p>		<p>
	The following CMS utility command modules relate to <var class="product">Model 204</var>. ~~Unlike the commands described so far in this book, however~~, you cannot issue CMS utility commands from within the <var class="product">Model 204</var> environment. For more information on CMS, refer to the <var class="book">[http://docs.rocketsoftware.com/nxt/gateway.dll/RKBnew556%2Fmodel%20204%2Fprevious%20versions%2Fv7.4%2Fm204_installzvm_v74.pdf Rocket Model 204 Installation Guide for IBM z/VM, version 7.4]</var>.</p>		The following CMS utility command modules relate to <var class="product">Model 204</var>. However, you cannot issue CMS utility commands from within the <var class="product">Model 204</var> environment. For more information on CMS, refer to the <var class="book">[http://docs.rocketsoftware.com/nxt/gateway.dll/RKBnew556%2Fmodel%20204%2Fprevious%20versions%2Fv7.4%2Fm204_installzvm_v74.pdf Rocket Model 204 Installation Guide for IBM z/VM, version 7.4]</var>.</p>

	==M204APND: Concatenating file definitions==		==M204APND: Concatenating file definitions==

ELowell at 20:58, 1 February 2016

2016-02-01T20:58:03Z

← Older revision		Revision as of 20:58, 1 February 2016
Line 3:		Line 3:
	==Overview==		==Overview==
	<p>		<p>
	The following CMS utility command modules relate to <var class="product">Model 204</var>. Unlike the commands described so far in this book, however, you cannot issue CMS utility commands from within the <var class="product">Model 204</var> environment. For more information on CMS, refer to the <var class="book">Model~~ ~~204 z/VM ~~Installation Guide~~</var>.</p>		The following CMS utility command modules relate to <var class="product">Model 204</var>. Unlike the commands described so far in this book, however, you cannot issue CMS utility commands from within the <var class="product">Model 204</var> environment. For more information on CMS, refer to the <var class="book">[http://docs.rocketsoftware.com/nxt/gateway.dll/RKBnew556%2Fmodel%20204%2Fprevious%20versions%2Fv7.4%2Fm204_installzvm_v74.pdf Rocket Model 204 Installation Guide for IBM z/VM, version 7.4]</var>.</p>

	==M204APND: Concatenating file definitions==		==M204APND: Concatenating file definitions==
Line 581:		Line 581:

	</div> <!-- end of toc limit div -->		</div> <!-- end of toc limit div -->

			[[Category: Commands]]

JAL: converted from 7.4 Command Ref manual

2014-07-01T15:13:55Z

converted from 7.4 Command Ref manual

New page

<div class="toclimit-2">

==Overview==

The following CMS utility command modules relate to <var class="product">Model 204</var>. Unlike the commands described so far in this book, however, you cannot issue CMS utility commands from within the <var class="product">Model 204</var> environment. For more information on CMS, refer to the <var class="book">Model 204 z/VM Installation Guide</var>.

==M204APND: Concatenating file definitions==

====Privileges====

Any user

====Function====

Permits concatenation of file definitions for <var class="product">Model 204</var>

====Syntax====
M204APND ddname parameter [, parameter]...
[[option] [, option]...]


Where:

<ul>
<li><var class="term">ddname</var> specifies the file to which the file defined is concatenated.</li>

<li><var class="term">parameter</var> is a standard <var>FILEDEF</var> or <var>M204FDEF</var> parameter. </li>

<li><var class="term">option</var> is a standard <var>FILEDEF</var> or <var>M204FDEF</var> option.</li>
</ul>

====Syntax notes====

A <var>FILEDEF</var> command with the <var>CLEAR</var> parameter for a <var class="term">ddname</var> that represents a concatenation of files clears all file definitions in the concatenation.

====Usage notes====

This module defines a file to be added to another file of a specified name. Concatenated files are processed in the order that the associated <var>FILEDEF</var>, <var>M204FDEF</var>, and <var>M204APND</var> commands are issued.

==M204CMS: Providing the interface between Model 204 and CMS==

====Privileges====

Any user

====Function====

Provides the interface between <var class="product">Model 204</var> and CMS

====Syntax====
M204CMS [module] [keyword=value [, keyword=value] ...


Where:

<ul>
<li><var class="term">module</var> specifies the name of the <var class="product">Model 204</var> program module to be executed. The default is <var>M204ONLN</var>.</li>

<li><var class="term">keyword</var> and its associated <var class="term">value</var> specify parameters passed to the <var class="product">Model 204</var> module in the format of an z/OS PARM field.</li>
</ul>

====Syntax notes====

The keyword and value are separated by an equal sign and inserted in the PARM field. Successive keyword-value pairs are separated by commas. An exception occurs when value is specified as a percent sign (<tt>%</tt>). In this case, only the keyword is inserted in the PARM field, with commas separating neighboring operands.

====Usage notes====

The <var>M204CMS</var> command is the interface between <var class="product">Model 204</var> and CMS. It is used during execution of a variety of <var class="product">Model 204</var> facilities to provide system services in the CMS environment. The M204CMS module is usually employed in EXEC procedures that provide higher-level interfaces to <var class="product">Model 204</var> (for example, FASTLOAD, ONLINE). 

==M204CRYP: Decoding features distributed in object/source form==

====Privileges====

Restricted

====Function====

Decodes key components of <var class="product">Model 204</var> features distributed in object and/or source code form

====Syntax====
M204CRYP [DECODE | ENCODE} featurename key [options]


Where:

<ul>
<li><var>ENCODE</var> causes the CCA XENCDEC program to encrypt vital elements of a specified feature. This disables the feature and prevents subsequent use, unless a <var>DECODE</var> request is made. <var>ENCODE</var> is used internally at Rocket Software.</li>

<li><var>DECODE</var> causes the CCA XENCDEC program to decrypt vital elements of a specified feature. This enables the feature.</li>

<li><var class="term">featurename</var> is a valid feature name, as defined in the CMS table M204CRYP FEATTBLE.</li>

<li><var class="term">key</var> is an eight-byte numeric character representation of a Rocket-supplied code, which is the trigger for encrypting or decrypting a specified feature.</li>

<li><var class="term">options</var> are:
<ul>
<li><var>NOREPLACE</var> checks that files with the same file ID as the output file to be generated by M204CRYP do not already exist. If one or more output files do exist, an error message is displayed and the M204CRYP command terminates. This option is the default to prevent existing files from inadvertently being destroyed.</li>

<li><var>REPLACE</var> causes the output file to be generated by <var>M204CRYP</var> to replace an existing file with the same file identifier.</li>
</ul></li>
</ul>

====Syntax notes====

The <var>M204CRYP</var> command has restricted use and must be issued directly from the MAINT204 machine (<var class="product">Model 204</var>'s maintenance virtual machine).

====M204CRYP report====

The <var>M204CRYP</var> command generates a report that is identified by a CMS file name equal to a feature name and a file type of D_REPT. The report contains:

<table>
<tr><td>FILE IN-CMS</td><td>File ID of the input file.</td></tr>

<tr><td>FILE OUT-CMS</td><td>File ID of the output file.</td></tr>

<tr><td>CONTROL PARM</td><td>Function used (DECODE) and the key value.</td></tr>

<tr><td>NUMBER OF RECORDS PROCESSED</td><td>Total number of records processed.</td></tr>

<tr><td colspan=2>Return codes and messages.</td></tr>
</table>

====M204CRYP return codes and messages====
The return codes issued by <var>M204CRYP</var> are described in the following table:
<table>
<tr class="head">
<th> Code </th>
<th> Message </th>
<th> Description </th>
</tr>

<tr>
<td> 0 </td>
<td> Successful completion </td>
<td> All materials were decrypted successfully. </td>
</tr>

<tr>
<td> 1 </td>
<td> Error in an input argument </td>
<td> The error may be a misspelling, an invalid option, or invalid decryption key. Check the command you issued, correct the error, and re-execute it. </td>
</tr>

<tr>
<td> 2 </td>
<td> Error in M204CRYP </td>
<td> This internally detected error return code is not used. </td>
</tr>

<tr>
<td> 3 </td>
<td> Execution of a host, CMS or CP, command failed </td>
<td> The return code and the text of the command are described in an error message. This usually means that the decryption utility failed for some reason. If this is the case, the D_REPT file shows the reason for the decryption failure. Check the report, correct the error, and rerun the M204CRYP command. </td>
</tr>
</table>

The following table lists the return codes and messages that appear in the report produced by the decryption utility. The appropriate diagnostic action is also suggested.
<table>
<tr class="head">
<th> Code </th>
<th> Message </th>
<th> Diagnostic action </th>
</tr>

<tr>
<td> 0 </td>
<td> None </td>
<td> None — decryption was successful. </td>
</tr>

<tr>
<td> 8 </td>
<td> No Control or Parm provided </td>
<td> <code>PARM=</code> on the EXEC card was invalid or missing. This reflects an internal error in the service routine used by M204CRYP. [[Contacting Rocket Software Technical Support|Contact Technical Support]] for assistance. </td>
</tr>

<tr>
<td> 12 </td>
<td> Invalid command specified </td>
<td><var>DECODE</var> was not specified on the <code>PARM=</code> on the EXEC card. This reflects an internal error in the service routines used by M204CRYP. [[Contacting Rocket Software Technical Support|Contact Technical Support]] for assistance. </td>
</tr>

<tr>
<td> 16 </td>
<td> Invalid decryption key specified </td>
<td> Decryption key specified was not exactly eight bytes in length. Verify that the key you have specified correctly matches the key you were supplied by Rocket. </td>
</tr>

<tr>
<td> 20 </td>
<td> Wrong decryption key specified </td>
<td> Decryption key specified does not match the key used to encrypt modules for the feature that you are installing. Verify that the key you have specified correctly matches the key you were supplied by Rocket. </td>
</tr>

<tr>
<td> 24 </td>
<td> Internal decryption xxxx error detected, where xxxx can be:
<ul>
<li>Clear text length</li>

<li>Clear checksum</li>

<li>Cipher checksum</li>
</ul></td>

<td> Decryption key specified does not match the key used to encrypt modules for the feature that you are installing, or the material you are trying to decrypt has been modified or tampered with. Verify that the key you have specified correctly matches the key you were supplied by Rocket. </td>
</tr>
</table>

==M204FDEF: Creating file definitions==

====Privileges====

Any user

====Function====

Permits creation of file definitions for files on unaccessed variable-format disks

====Syntax====
M204FDEF ddname address DSN dsnname
[parameter [, parameter] ...]


Where:

<ul>
<li><var class="term">ddname</var> is the name associated with the file to be defined.</li>

<li><var class="term">address</var> is the virtual address of the minidisk where the file to be processed resides. The address can be up to four digits long.</li>

<li><var>DSN</var> is the identifier tag for the dataset.</li>

<li><var class="term">dsname</var> is the name of the dataset. The dataset name follows the <var>DSN</var> tag. A blank space must separate the tag and the name. The same conventions and restrictions associated with the <var>DSN</var> operand of the <var>FILEDEF</var> command apply. You specify the dataset name as a series of items separated by blanks. For example:

DOSRV.M204.CLIENTS

is represented as:

DOSRV M204 CLIENTS</li>

<li><var class="term">parameter</var> is a standard FILEDEF option, the same as is used for dataset definition with z/OS. The DSORG, RECFM, BLKSIZE, and LRECL options are particularly useful with <var class="product">Model 204</var>.</li>
</ul>

====Usage notes====

The CMS FILEDEF command requires that any variable-format disk used by <var class="product">Model 204</var> be accessed through the CMS ACCESS command. This limits the total disks available to a particular <var class="product">Model 204</var> service virtual machine. The <var>M204FDEF</var> module overcomes the limitation. 


By performing a modified FILEDEF function, <var>M204FDEF</var> permits the definition of non-CMS disks without accessing the volume on which the variable format files reside. The non-CMS disks act as substitute volumes. The <var class="product">Model 204</var> user can, therefore, establish an unlimited number of file definitions on any number of disks.

==M204LDEF: Specifying tape label information==

====Privileges====

Any user

====Function====

Permits specification of magnetic tape label information for tape volumes defined using the <var>M204APND</var> module

====Syntax====
M204LEDF ddname parameter [, parameter] ...
[option [, option] ...]


Where:

<ul>
<li><var class="term">ddname</var> is the name associated with the file to be defined.</li>

<li><var class="term">parameter</var> is a standard LABELDEF parameter.</li>

<li><var class="term">option</var> is a standard LABELDEF option.</li>
</ul>

====Syntax notes====

A LABELDEF command that specifies the CLEAR parameter for a <var class="term">ddname</var> that represents a label definition for a concatenated file clears only the first label definition in the concatenation.

====Usage notes====

Using the <var>M204APND</var> command, you can define a file as a concatenation of magnetic tape volumes. You must issue a LABELDEF command for each volume in the concatenation. For more information about the LABELDEF command, refer to your IBM documentation. Because a label definition is associated with a file definition through the ddname parameter, an alternative is required to define labels for the second and subsequent volumes of a multi-reel file. <var>M204LDEF</var> provides this function. 


<var>M204LDEF</var> commands are associated with the file definitions created by the <var>M204APND</var> command in the sequence that the file definitions are established.

For information on the FILEDEF options, refer to [[Defining the runtime environment (CCAIN)]]. 


For information about using <var>M204LDEF</var> and <var>M204APND</var> to back up and restore multitape <var class="product">Model 204</var> files, see [[File dumping and restoring#Backing up and restoring multitape files under z/VM|Backing up and restoring multitape files under z/VM]].

==M204SQSH: Condensing map sizes==

====Privileges====

Any user

====Function====

Condenses the in-storage load map for a program loaded through a LOAD or LOADMOD command. The <var>M204SQSH</var> program reduces the map size by eliminating all load map entries that are not section definitions.

====Syntax====
M204SQSH


====Syntax notes====
The <var>M204SQSH</var> module is used by the <var>M204GEN</var> and <var>M204XGEN</var> commands to construct various <var class="product">Model 204</var> programs. 

==M204UTIL: Maintaining variable-format volumes==

====Privileges====

Any user

====Function====

Initializes variable-format volumes and allocates, renames, and erases datasets on such volumes

====Syntax====
M204UTIL function operands ([option [, option] ...


Where:

<ul>
<li><var class="term">function</var> specifies the operation that <var>M204UTIL</var> performs. Function is one of the following operations:
<ul>
<li> ALLOCATE</li>

<li> ERASE</li>

<li> INITIAL</li>

<li> LABEL</li>

<li> LIST </li>

<li> RENAME</li>
</ul></li>

<li><var class="term">operands</var> are dependent on the kind of function specified. An operand can be a dataset name, a virtual address, or whatever represents the object of the function. Minidisk addresses must be specified as three or four digits.</li>

<li><var class="term">option</var> is an attribute of an operand and depends on the kind of function specified. </li>
</ul>

====Usage notes====
<ul>
<li>The format of the M204UTIL module depends on the function chosen. The individual formats are described in the following sections:
:[[#M204UTIL ALLOCATE: Allocating space for a variable-format minidisk|M204UTIL ALLOCATE: Allocating space for a variable-format minidisk]]
:[[#M204UTIL ERASE: Erasing a data set on a variable-format disk|M204UTIL ERASE: Erasing a data set on a variable-format disk]]
:[[#M204UTIL INITIAL: Initializing a variable-format volume|M204UTIL INITIAL: Initializing a variable-format volume]]
:[[#M204UTIL LABEL: Changing a variable-format minidisk label|M204UTIL LABEL: Changing a variable-format minidisk label]]
:[[#M204UTIL LIST: Listing data sets on a variable-format minidisk|M204UTIL LIST: Listing data sets on a variable-format minidisk]]
:[[#M204UTIL RENAME: Changing a data set name on a variable-format minidisk|M204UTIL RENAME: Changing a data set name on a variable-format minidisk]]. </li>

<li>Shared DASD: M204UTIL uses reserve/release logic when it updates the Volume Table of Contents (VTOC) of a variable-format disk. Consequently, it can manipulate a volume used by one or more <var class="product">Model 204</var> service virtual machines. However, erasing data sets on such volumes while they are being used by <var class="product">Model 204</var> causes unpredictable results.</li>
</ul>

==M204UTIL ALLOCATE: Allocating space for a variable-format minidisk==

====Privileges====

Any user

====Function====

Allocates file space on the variable-format minidisk

====Syntax====
M204UTIL ALLOCATE datasetname {mode | address} (
{PRIMARY nnnnnn CYL | TRK | BLK}
[DSORG PS | DA] [RECFM format] [BLKSIZE nnnnn]
[LRECL nnnnn]


Where:
<ul>
<li><var>ALLOCATE</var> has the alias <var>CREATE</var>. <var>M204UTIL CREATE</var> is functionally equivalent to <var>M204UTIL ALLOCATE</var>. </li>

<li><var class="term">datasetname</var> specifies the components, separated by blanks, of the file name for which space is allocated.</li>

<li><var class="term">mode</var> specifies the disk mode of the minidisk where the file is to be allocated.</li>

<li><var class="term">address</var> specifies the hexadecimal virtual address of the minidisk where the file allocation is to be performed. </li>

<li><var>PRIMARY nnnnnn</var> specifies the primary allocation quantity in cylinders (CYL) or tracks (TRK) for a count key data device, or in blocks (BLKS) for a fixed-block architecture device. This option must be specified.</li>

<li><var>DSORG PS|DA</var> specifies the dataset organization. If this option is omitted, no dataset organization is defined.</li>

<li><var>RECFM format</var> specifies the dataset record format. If this option is omitted, no record format is defined.</li>

<li><var>BLKSIZE nnnnn</var> specifies the dataset block size. If this option is omitted, a value of 0 is used.</li>

<li><var>LRECL nnnnn</var> specifies the dataset logical record length. If this option is omitted, a value of 0 is used.</li>
</ul>

==M204UTIL ERASE: Erasing a dataset on a variable-format disk==

====Privileges====

Any user

====Function====

Erases a dataset on a variable-format disk

====Syntax====
M204UTIL ERASE datasetname {mode | address}


Where:

<ul>
<li><var>ERASE</var> has the aliases <var>SCRATCH</var> and <var>REMOVE</var>. <var>M204UTIL SCRATCH</var> and <var>M204UTIL REMOVE</var> are functionally equivalent to <var>M204UTIL ERASE</var>. </li>

<li><var class="term">datasetname</var> specifies the qualifiers, separated by blanks, that make up the name of the dataset to be erased.</li>

<li><var class="term">mode</var> indicates the disk mode of the minidisk from which the file is to be erased.</li>

<li><var class="term">address</var> specifies the hexadecimal virtual address designating the minidisk. </li>
</ul>

==M204UTIL INITIAL: Initializing a variable-format volume==

====Privileges====

Any user

====Function====

Initializes a volume in variable format

====Syntax====
M204UTIL INITIAL address label
([LOCATION nnnnnn | EXTENT nnnnnn]


Where:

<ul>
<li><var>INITIAL</var> has the alias <var>FORMAT</var>. <var>M204UTIL FORMAT</var> is functionally equivalent to <var>M204UTIL INITIAL</var>.</li>

<li><var class="term">address</var> is the hexadecimal virtual address of the minidisk to be initialized.</li>

<li><var class="term">label</var> is the volume label.</li>

<li><var>LOCATION nnnnnn</var> specifies the starting location of the Volume Table of Contents (VTOC) as a track or block number. If a value is not specified, the default option for a count key data device is <code>LOCATION 1</code>. For a fixed-block architecture device, the default option is <code>LOCATION 2</code>.</li>

<li><var>EXTENT nnnnnn</var> specifies the size of the VTOC in tracks or blocks. If a value is not specified, the default option for a count key data device is <code>EXTENT 2</code>. For a fixed-block architecture device, the default option is a value that causes the VTOC to occupy the remaining portion of the first cyclical group in the device. </li>
</li>
</ul>

<var class="product">Model 204</var> does not support VTOCs that cross cylinder boundaries on count-key-data devices. Indexed VTOCs are neither created nor manipulated by <var class="product">Model 204</var>.

====Usage notes====

Do not use the <var>M204UTIL INITIAL</var> function on volumes that are owned by virtual machines other than the <var>MODEL204</var> virtual machine, for example, other operating systems, or minidisks that contain data that you want to keep. 

The initialization process deletes the VTOC, which has the pointers to the z/OS datasets on the disk, and <var class="product">Model 204</var> can no longer find the datasets. 


Enter <code>YES</code> and not Y in response to the confirmation prompt. 

==M204UTIL LABEL: Changing a variable-format minidisk label==

====Privileges====

Any user

====Function====

Changes the label of a variable-format minidisk

====Syntax====
M204UTIL LABEL address label


Where:

<ul>
<li><var class="term">address</var> specifies the hexadecimal virtual address of the minidisk to be labeled.</li>

<li><var class="term">label</var> specifies the volume label to be assigned to the minidisk. </li>
</ul>

==M204UTIL LIST: Listing datasets on a variable-format minidisk==

====Privileges====

Any user

====Function====

Lists the datasets on a variable-format minidisk

====Syntax====
M204UTIL LIST datasetname {mode | address}


Where:

<ul>
<li><var class="term">datasetname</var> specifies the qualifiers, separated by blanks, that comprise the name of the dataset that is to be listed.

If the last qualifier specified is an asterisk (*), all dataset names that begin with the prefix defined by the preceding qualifiers are listed. If the last qualifier specified ends with an asterisk (*), the response includes all datasets whose names begin with the preceding qualifiers and are followed by a qualifier that matches the last one up to the asterisk.

If the only qualifier specified is an asterisk (*), all datasets on the volume are listed.
</li>

<li><var class="term">mode</var> specifies the disk mode of the minidisk that contains the files to be listed.</li>

<li><var class="term">address</var> specifies the hexadecimal virtual address designating the minidisk. </li>
</ul>

==M204UTIL RENAME: Changing a dataset name on a variable-format minidisk==

====Privileges====

Any user

====Function====

Changes the name of a dataset on a variable-format minidisk

====Syntax====
M204UTIL RENAME oldname {mode | address} (newname


Where:


<var>RENAME</var> has the alias <var>CHANGE</var>. <var>M204UTIL CHANGE</var> is functionally equivalent to <var>M204UTIL RENAME</var>.

<ul>
<li><var class="term">oldname</var> specifies the qualifiers, separated by blanks, that make up the name of the dataset to be renamed.</li>

<li><var class="term">mode</var> indicates the disk mode of the minidisk on which the file to be renamed resides.</li>

<li><var class="term">address</var> specifies the hexadecimal virtual address designating the minidisk.</li>

<li><var class="term">newname</var> specifies the qualifiers, separated by blanks, that make up the new name to be assigned to the dataset. </li>
</ul>

==M204XFER: Invoking the M204CMS module in the DCSS==

====Privileges====

Any user

====Function====

Transfers control to the version of the M204CMS module that executes in a discontiguous saved segment (DCSS)

====Syntax====
XFER program interface [(selection [, selection] ...]


Where:

<ul>
<li><var class="term">program</var> specifies the name of the <var class="product">Model 204</var> program segment, for example, <var>M204ONLN</var> or <var>M204IFM1</var>, that is to be invoked. If this operand is omitted, the default value of <var>M204ONLN</var> is used. Entering an asterisk (<tt>*</tt>) for this option indicates that no program segment is to be invoked.</li>

<li><var class="term">interface</var> specifies the name of the <var class="product">Model 204</var> CMS interface segment, for example, <var>M204CMS</var>, or the user interface segment, for example, <var>M204USR</var>. If it is omitted, the default is <var>M204CMS</var>.</li>

<li><var class="term">selection</var> is an option that is passed to the <var>M204CMS</var> module intact.</li>
</ul>

====Usage notes====
<ul>
<li>For this module to function, the specified interface segment (<var>M204CMS</var> by default) must be defined. If this segment is not created, the <var>M204XFER</var> module must not be generated. If the <var>M204XFER</var> module exists and the interface segment does not, <var>M204XFER</var> abandons any attempt to invoke <var class="product">Model 204</var>.</li>

<li><var>M204XFER</var> can optionally load a second DCSS containing the <var class="product">Model 204</var> program that is to be invoked by <var>M204CMS</var>.


<var>M204XFER</var> first attempts to load the specified program segment. Regardless of whether this operation succeeds, it then attempts to load the interface segment. If this attempt fails, <var>M204XFER</var> terminates with an error message. Otherwise, the interface is invoked in the DCSS with the same parameter list that was used to invoke <var>M204XFER</var>. 


If the specified program segment could not be loaded by <var>M204XFER</var>, a MODULE that has the same name as the segment is loaded by <var>M204FCMS</var>. </li>
</ul>

</div> 

[[Category:CMS utility commands]]

CMS utility command modules - Revision history

ELowell at 21:53, 26 October 2017

ELowell: /* Overview */

ELowell at 20:58, 1 February 2016

JAL: remove category link

JAL: converted from 7.4 Command Ref manual

← Older revision		Revision as of 21:53, 26 October 2017
Line 3:		Line 3:
	==Overview==		==Overview==
	<p>		<p>
	The following CMS utility command modules relate to <var class="product">Model 204</var>. However, you cannot issue CMS utility commands from within the <var class="product">Model 204</var> environment. For more information on CMS, refer to the <var class="book">[~~http~~:~~//docs.rocketsoftware.com/nxt/gateway.dll/RKBnew556%2Fmodel%20204%2Fprevious%20versions%2Fv7.4%2Fm204_installzvm_v74~~.pdf Rocket Model 204 Installation Guide for IBM z/VM, version 7.4]</var>.</p>		The following CMS utility command modules relate to <var class="product">Model 204</var>. However, you cannot issue CMS utility commands from within the <var class="product">Model 204</var> environment. For more information on CMS, refer to the <var class="book">[[Media:M204_InstallzVM_V74.pdf \|
			Rocket Model 204 Installation Guide for IBM z/VM, version 7.4]]</var>.</p>

	==M204APND: Concatenating file definitions==		==M204APND: Concatenating file definitions==

← Older revision		Revision as of 15:38, 1 July 2014
Line 581:		Line 581:

	</div> <!-- end of toc limit div -->		</div> <!-- end of toc limit div -->

	~~[[Category:CMS utility commands]]~~