Category:Operator commands - Revision history

Dme: /* Issuing MODIFY or SMSG operator commands */

2017-10-03T20:22:55Z

Issuing MODIFY or SMSG operator commands

← Older revision		Revision as of 20:22, 3 October 2017
Line 32:		Line 32:

	Responses to SMSG commands are sent via MSGNOH, if the SirTune/Model 204 service machine is authorized to use MSGNOH, and via MSG otherwise.		Responses to SMSG commands are sent via MSGNOH, if the SirTune/Model 204 service machine is authorized to use MSGNOH, and via MSG otherwise.

			===Example===

			The following command, issued from SDSF or some equivalent, will interrupt and restart, with a snap, user <i>n</i> running in job <i>jobname</i>:

			<p class="code">/F <i>jobname</i>,RESTART 0C4 USER <i>n</i></p>

	==PDF of category pages==		==PDF of category pages==

Dme: /* Issuing MODIFY or SMSG operator commands */

2017-10-03T19:07:57Z

Issuing MODIFY or SMSG operator commands

← Older revision		Revision as of 19:07, 3 October 2017
Line 12:		Line 12:
	The RESTART utility and SirTune commands require a certain level of authorization. Under MVS, any user that is capable of issuing a <code>MODIFY</code> command is considered to be authorized to issue operator commands. Under CMS, a user must be authorized to issue these commands. This authorization is accomplished via the <var>[[RESTAUTH command\|RESTAUTH]]</var> command if the RESTART utility is handling operator commands, and via the <code>AUTHORIZE</code> command in SIRTUNEI if SirTune is handling operator commands.		The RESTART utility and SirTune commands require a certain level of authorization. Under MVS, any user that is capable of issuing a <code>MODIFY</code> command is considered to be authorized to issue operator commands. Under CMS, a user must be authorized to issue these commands. This authorization is accomplished via the <var>[[RESTAUTH command\|RESTAUTH]]</var> command if the RESTART utility is handling operator commands, and via the <code>AUTHORIZE</code> command in SIRTUNEI if SirTune is handling operator commands.

	==Issuing MODIFY or SMSG operator commands==		==<b id="oprCmdFmt"></b>Issuing MODIFY or SMSG operator commands==
	Under MVS, you can issue operator commands using the <code>MODIFY</code> operator command. This command can be issued at an operator console or under SDSF or equivalent virtual console system. For example, to issue the <code>STATUS</code> command to SirTune running under job PRODONLN under SDSF's LOG screen, you can simply enter:		Under MVS, you can issue operator commands using the <code>MODIFY</code> operator command. This command can be issued at an operator console or under SDSF or equivalent virtual console system. For example, to issue the <code>STATUS</code> command to SirTune running under job PRODONLN under SDSF's LOG screen, you can simply enter:

JAL: misc formatting

2016-05-02T16:05:00Z

misc formatting

JAL: /* PDF of category pages */

2014-12-04T21:15:58Z

PDF of category pages

← Older revision		Revision as of 21:15, 4 December 2014
Line 35:		Line 35:

	==PDF of category pages==		==PDF of category pages==
	You can <b><span class="plainlinks">[{{fullurl:{{FULLPAGENAMEE}}\|action=pdfbook}} use this link]</span></b> to create a PDF file that contains all the pages in this category. ~~For each subcategory~~, ~~this~~ PDF will also contain a linked list of ~~its constituent~~ pages.		You can <b><span class="plainlinks">[{{fullurl:{{FULLPAGENAMEE}}\|action=pdfbook}} use this link]</span></b> to create a PDF file that contains all the pages in this category. If this category contains a "Subcategories" section, the PDF will also contain a linked list of the pages that belong to each subcategory listed in the "Subcategories" section.

	<p class="note"><b>Note:</b> The resulting PDF is not optimized for online use. All blue links except for those in the table of contents (TOC) take you outside of the PDF (typically to http://m204wiki.rocketsoftware.com), so you must rely on the PDF bookmarks and TOC for online navigation. Hovering your mouse over a link will reveal its destination. </p>		<p class="note"><b>Note:</b> The resulting PDF is not optimized for online use. All blue links except for those in the table of contents (TOC) take you outside of the PDF (typically to http://m204wiki.rocketsoftware.com), so you must rely on the PDF bookmarks and TOC for online navigation. Hovering your mouse over a link will reveal its destination. </p>

	[[Category:Commands\| Operator]]		[[Category:Commands\| Operator]]

JAL: /* PDF */

2014-11-21T21:33:39Z

PDF

← Older revision		Revision as of 21:33, 21 November 2014
Line 34:		Line 34:
	Responses to SMSG commands are sent via MSGNOH, if the SirTune/Model 204 service machine is authorized to use MSGNOH, and via MSG otherwise.		Responses to SMSG commands are sent via MSGNOH, if the SirTune/Model 204 service machine is authorized to use MSGNOH, and via MSG otherwise.

	==PDF==		==PDF of category pages==
	You can [{{fullurl:{{FULLPAGENAMEE}}\|action=pdfbook}} use this link] to create a PDF file that contains all the pages in this category.		You can <b><span class="plainlinks">[{{fullurl:{{FULLPAGENAMEE}}\|action=pdfbook}} use this link]</span></b> to create a PDF file that contains all the pages in this category. For each subcategory, this PDF will also contain a linked list of its constituent pages.

			<p class="note"><b>Note:</b> The resulting PDF is not optimized for online use. All blue links except for those in the table of contents (TOC) take you outside of the PDF (typically to http://m204wiki.rocketsoftware.com), so you must rely on the PDF bookmarks and TOC for online navigation. Hovering your mouse over a link will reveal its destination. </p>

	[[Category:Commands\| Operator]]		[[Category:Commands\| Operator]]

JAL at 16:46, 8 July 2014

2014-07-08T16:46:36Z

← Older revision		Revision as of 16:46, 8 July 2014
Line 1:		Line 1:
	~~''Sirius~~ commands'' available to the system operator via the MVS console, MODIFY command or via the VM SMSG facility.		These are commands available to the system operator via the MVS console, MODIFY command, or via the VM SMSG facility.

	Some standard [[Model 204]] commands, such as [[SIRIUS command\|SIRIUS]] or [[STATUS command\|STATUS]], may also be issued by replying to the pending HALT message. While these are also operator commands in some sense, this list focuses on operator commands issued via MODIFY or SMSG. The term operator command refers specifically to commands issued via MODIFY or SMSG.		Some standard [[Model 204]] commands, such as [[SIRIUS command\|SIRIUS]] or [[STATUS command\|STATUS]], may also be issued by replying to the pending HALT message. While these are also operator commands in some sense, this list focuses on operator commands issued via <var>MODIFY</var> or <var>SMSG</var>. The term operator command refers specifically to commands issued via <var>MODIFY</var> or <var>SMSG</var>.

	==Versions and availability==		==Versions and availability==

JAL: /* Versions and availability */

2014-07-08T16:43:53Z

Versions and availability

← Older revision		Revision as of 16:43, 8 July 2014
Line 4:		Line 4:

	==Versions and availability==		==Versions and availability==

	Before Sirius Mods version 6.9, the RESTART facility had to be enabled by setting the X'01' bit in the system RESTARTU parameter before any of these commands were available. The RESTARTU system parameter must be set in the EXEC card PARM parameter under MVS or on the command which starts the Online under CMS. Before Sirius Mods version 6.9, MODIFY or SMSG command support could also be provided by SirTune, which would run as a separate load module that ran Model 204 as a subtask.		Before Sirius Mods version 6.9, the RESTART facility had to be enabled by setting the X'01' bit in the system RESTARTU parameter before any of these commands were available. The RESTARTU system parameter must be set in the EXEC card PARM parameter under MVS or on the command which starts the Online under CMS. Before Sirius Mods version 6.9, MODIFY or SMSG command support could also be provided by SirTune, which would run as a separate load module that ran Model 204 as a subtask.

	The format of the [[SirTune ~~MODIFY/SMSG~~]] ~~commands~~ is documented separately. However, under Sirius Mods version 6.9 and later, the SirTune data collector is integrated into the Sirius Mods, so it runs as part of the Model 204 load module. Since SirTune is effectively part of the Sirius Mods as of that release, its operator commands are also documented here. The format of many of the SirTune and RESTART utility commands are identical, or at least similar. Any differences between the command formats are noted under the documentation for the command.		The format of the <var>MODIFY</var> and <var>SMSG</var> commands for [[SirTune]] is documented separately. However, under Sirius Mods version 6.9 and later, the SirTune data collector is integrated into the Sirius Mods, so it runs as part of the Model 204 load module. Since SirTune is effectively part of the Sirius Mods as of that release, its operator commands are also documented here. The format of many of the SirTune and RESTART utility commands are identical, or at least similar. Any differences between the command formats are noted under the documentation for the command.

	If the RESTART utility is started in an ONLINE (or BATCH204) job that is running with SirTune, the RESTART utility defers to SirTune and allows SirTune to provide the required functionality. Under Sirius Mods version 6.9 and later, if an Online is brought up under the standalone SirTune load module, the SirTune integrated with the Sirius Mods will defer to the standalone SirTune. However, this is not a recommended configuration — ''the standalone SirTune load module should not be used with Sirius Mods version 6.9 and later''.		If the RESTART utility is started in an ONLINE (or BATCH204) job that is running with SirTune, the RESTART utility defers to SirTune and allows SirTune to provide the required functionality. Under Sirius Mods version 6.9 and later, if an Online is brought up under the standalone SirTune load module, the SirTune integrated with the Sirius Mods will defer to the standalone SirTune. However, this is not a recommended configuration — ''the standalone SirTune load module should not be used with Sirius Mods version 6.9 and later''.

	The RESTART utility and SirTune commands require a certain level of authorization. Under MVS, any user that is capable of issuing a MODIFY command is considered to be authorized to issue operator commands. Under CMS, a user must be authorized to issue these commands. This authorization is accomplished via the RESTAUTH command if the RESTART utility is handling operator commands, and via the [[AUTHORIZE]] command in SIRTUNEI if SirTune is handling operator commands.		The RESTART utility and SirTune commands require a certain level of authorization. Under MVS, any user that is capable of issuing a MODIFY command is considered to be authorized to issue operator commands. Under CMS, a user must be authorized to issue these commands. This authorization is accomplished via the RESTAUTH command if the RESTART utility is handling operator commands, and via the <var>AUTHORIZE</var> command in SIRTUNEI if SirTune is handling operator commands.

	==Issuing MODIFY or SMSG operator commands==		==Issuing MODIFY or SMSG operator commands==

JAL: /* Issuing MODIFY or SMSG operator commands */

2013-03-08T01:57:05Z

Issuing MODIFY or SMSG operator commands

← Older revision		Revision as of 01:57, 8 March 2013
Line 17:		Line 17:
	Under MVS, you can issue operator commands using the MODIFY operator command. This command can be issued at an operator console or under SDSF or equivalent virtual console system. For example, to issue the STATUS command to SirTune running under job PRODONLN under SDSF's LOG screen, you can simply enter		Under MVS, you can issue operator commands using the MODIFY operator command. This command can be issued at an operator console or under SDSF or equivalent virtual console system. For example, to issue the STATUS command to SirTune running under job PRODONLN under SDSF's LOG screen, you can simply enter

	/MODIFY PRODONLN,STATUS		<p class="code">/MODIFY PRODONLN,STATUS</p>

	or		or

	/F PRODONLN,STATUS		<p class="code">/F PRODONLN,STATUS </p>

	Responses to MODIFY commands go to the system log and should be viewable under SDSF.		Responses to MODIFY commands go to the system log and should be viewable under SDSF.
Line 27:		Line 27:
	Under CMS, these commands can be issued via the SMSG CP command. For example, to issue the STATUS command to SirTune running on a virtual machine named PRODONLN, you can simply enter		Under CMS, these commands can be issued via the SMSG CP command. For example, to issue the STATUS command to SirTune running on a virtual machine named PRODONLN, you can simply enter

	SMSG PRODONLN STATUS		<p class="code">SMSG PRODONLN STATUS </p>

	or		or

	CP SMSG PRODONLN STATUS		<p class="code">CP SMSG PRODONLN STATUS </p>

	Responses to SMSG commands are sent via MSGNOH, if the SirTune/Model 204 service machine is authorized to use MSGNOH, and via MSG otherwise.		Responses to SMSG commands are sent via MSGNOH, if the SirTune/Model 204 service machine is authorized to use MSGNOH, and via MSG otherwise.

JAL at 17:37, 9 October 2012

2012-10-09T17:37:31Z

← Older revision		Revision as of 17:37, 9 October 2012
Line 34:		Line 34:

	Responses to SMSG commands are sent via MSGNOH, if the SirTune/Model 204 service machine is authorized to use MSGNOH, and via MSG otherwise.		Responses to SMSG commands are sent via MSGNOH, if the SirTune/Model 204 service machine is authorized to use MSGNOH, and via MSG otherwise.

			==PDF==
			You can [{{fullurl:{{FULLPAGENAMEE}}\|action=pdfbook}} use this link] to create a PDF file that contains all the pages in this category.

	[[Category:Commands\| Operator]]		[[Category:Commands\| Operator]]

JAL2 at 21:13, 2 October 2012

2012-10-02T21:13:58Z

← Older revision		Revision as of 21:13, 2 October 2012
Line 35:		Line 35:
	Responses to SMSG commands are sent via MSGNOH, if the SirTune/Model 204 service machine is authorized to use MSGNOH, and via MSG otherwise.		Responses to SMSG commands are sent via MSGNOH, if the SirTune/Model 204 service machine is authorized to use MSGNOH, and via MSG otherwise.

	[[Category:Commands\|~Operator]]		[[Category:Commands\| Operator]]

← Older revision		Revision as of 16:05, 2 May 2016
Line 1:		Line 1:
	These are commands available to the system operator via the MVS console, MODIFY command, or via the VM SMSG facility.		These are commands available to the system operator via the MVS console, <code>MODIFY</code> command, or via the VM <code>SMSG</code> facility.

	Some standard [[Model 204]] commands, such as [[SIRIUS command\|SIRIUS]] or [[STATUS command\|STATUS]], may also be issued by replying to the pending HALT message. While these are also operator commands in some sense, this list focuses on operator commands issued via <~~var~~>MODIFY</~~var~~> or <~~var~~>SMSG</~~var~~>. The term operator command refers specifically to commands issued via <~~var~~>MODIFY</~~var~~> or <~~var~~>SMSG</~~var~~>.		Some standard [[Model 204]] commands, such as <var>[[SIRIUS command\|SIRIUS]]</var> or <var>[[STATUS command\|STATUS]]</var>, may also be issued by replying to the pending HALT message. While these are also operator commands in some sense, this list focuses on operator commands issued via <code>MODIFY</code> or <code>SMSG</code>. The term operator command refers specifically to commands issued via <code>MODIFY</code> or <code>SMSG</code>.

	==Versions and availability==		==Versions and availability==
	Before Sirius Mods version 6.9, the RESTART facility had to be enabled by setting the X'01' bit in the system RESTARTU parameter before any of these commands were available. ~~The~~ RESTARTU ~~system parameter~~ must be set in the EXEC card PARM parameter under MVS or on the command which starts the Online under CMS. Before Sirius Mods version 6.9, MODIFY or SMSG command support could also be provided by SirTune, which would run as a separate load module that ran Model 204 as a subtask.		Before Sirius Mods version 6.9, the RESTART facility had to be enabled by setting the X'01' bit in the system <var>[[RESTARTU parameter\|RESTARTU]]</var> parameter before any of these commands were available. <var>RESTARTU</var> must be set in the EXEC card PARM parameter under MVS or on the command which starts the Online under CMS. Before Sirius Mods version 6.9, MODIFY or SMSG command support could also be provided by [[SirTune]], which would run as a separate load module that ran Model 204 as a subtask.

	The format of the <~~var~~>MODIFY</~~var~~> and <~~var~~>SMSG</~~var~~> commands for [[SirTune]] is documented separately. However, under Sirius Mods version 6.9 and later, the SirTune data collector is integrated into the Sirius Mods, so it runs as part of the Model 204 load module. Since SirTune is effectively part of the Sirius Mods as of that release, its operator commands are also documented here. The format of many of the SirTune and RESTART utility commands are identical, or at least similar. Any differences between the command formats are noted under the documentation for the command.		The format of the <code>MODIFY</code> and <code>SMSG</code> commands for SirTune is documented separately. However, under Sirius Mods version 6.9 and later, the SirTune data collector is integrated into the Sirius Mods, so it runs as part of the Model 204 load module. Since SirTune is effectively part of the Sirius Mods as of that release, its operator commands are also documented here. The format of many of the SirTune and RESTART utility commands are identical, or at least similar. Any differences between the command formats are noted under the documentation for the command.

	If the RESTART utility is started in an ONLINE (or BATCH204) job that is running with SirTune, the RESTART utility defers to SirTune and allows SirTune to provide the required functionality. Under Sirius Mods version 6.9 and later, if an Online is brought up under the standalone SirTune load module, the SirTune integrated with the Sirius Mods will defer to the standalone SirTune. However, this is not a recommended configuration — ''the standalone SirTune load module should not be used with Sirius Mods version 6.9 and later''.		If the RESTART utility is started in an ONLINE (or BATCH204) job that is running with SirTune, the RESTART utility defers to SirTune and allows SirTune to provide the required functionality. Under Sirius Mods version 6.9 and later, if an Online is brought up under the standalone SirTune load module, the SirTune integrated with the Sirius Mods will defer to the standalone SirTune. However, this is not a recommended configuration — ''the standalone SirTune load module should not be used with Sirius Mods version 6.9 and later''.

	The RESTART utility and SirTune commands require a certain level of authorization. Under MVS, any user that is capable of issuing a MODIFY command is considered to be authorized to issue operator commands. Under CMS, a user must be authorized to issue these commands. This authorization is accomplished via the RESTAUTH command if the RESTART utility is handling operator commands, and via the <~~var~~>AUTHORIZE</~~var~~> command in SIRTUNEI if SirTune is handling operator commands.		The RESTART utility and SirTune commands require a certain level of authorization. Under MVS, any user that is capable of issuing a <code>MODIFY</code> command is considered to be authorized to issue operator commands. Under CMS, a user must be authorized to issue these commands. This authorization is accomplished via the <var>[[RESTAUTH command\|RESTAUTH]]</var> command if the RESTART utility is handling operator commands, and via the <code>AUTHORIZE</code> command in SIRTUNEI if SirTune is handling operator commands.

	==Issuing MODIFY or SMSG operator commands==		==Issuing MODIFY or SMSG operator commands==
			Under MVS, you can issue operator commands using the <code>MODIFY</code> operator command. This command can be issued at an operator console or under SDSF or equivalent virtual console system. For example, to issue the <code>STATUS</code> command to SirTune running under job PRODONLN under SDSF's LOG screen, you can simply enter:
	Under MVS, you can issue operator commands using the MODIFY operator command. This command can be issued at an operator console or under SDSF or equivalent virtual console system. For example, to issue the STATUS command to SirTune running under job PRODONLN under SDSF's LOG screen, you can simply enter

	<p class="code">/MODIFY PRODONLN,STATUS</p>		<p class="code">/MODIFY PRODONLN,STATUS</p>
Line 22:		Line 21:
	<p class="code">/F PRODONLN,STATUS </p>		<p class="code">/F PRODONLN,STATUS </p>

	Responses to MODIFY commands go to the system log and should be viewable under SDSF.		Responses to <code>MODIFY</code> commands go to the system log and should be viewable under SDSF.

	Under CMS, these commands can be issued via the SMSG CP command. For example, to issue the STATUS command to SirTune running on a virtual machine named PRODONLN, you can simply enter		Under CMS, these commands can be issued via the SMSG <code>CP</code> command. For example, to issue the <code>STATUS</code> command to SirTune running on a virtual machine named PRODONLN, you can simply enter

	<p class="code">SMSG PRODONLN STATUS </p>		<p class="code">SMSG PRODONLN STATUS </p>