SoftSpy messages - Revision history

ELowell at 23:24, 13 April 2017

2017-04-13T23:24:35Z

ELowell at 18:07, 2 November 2015

2015-11-02T18:07:59Z

← Older revision		Revision as of 18:07, 2 November 2015
Line 2,227:		Line 2,227:
	----		----

	===Messages 176~~-206~~===		===Messages 176 and higher===

	<table class="message"><tr><th>Number</th> <td>176</td></tr>		<table class="message"><tr><th>Number</th> <td>176</td></tr>
Line 2,501:		Line 2,501:
	<tr><th>Description</th> <td>An attempt was made to issue the SPY AUDIT ON or SPY AUDIT OFF command from a userid other than a system manager or user zero.		<tr><th>Description</th> <td>An attempt was made to issue the SPY AUDIT ON or SPY AUDIT OFF command from a userid other than a system manager or user zero.
	</td></tr>		</td></tr>
	<tr><th>Response</th> <td>Log on as a system manager and ~~re-issue~~ the command or issue the command from user zero.</td></tr></table>		<tr><th>Response</th> <td>Log on as a system manager and reissue the command or issue the command from user zero.</td></tr></table>

	----		----
Line 2,541:		Line 2,541:
	</td></tr>		</td></tr>

	<tr><th>Response</th> <td>Change the terminal model to 2, 3, or 4, then ~~re-issue~~ the SPY ON command.		<tr><th>Response</th> <td>Change the terminal model to 2, 3, or 4, then reissue the SPY ON command.
	<p> For example:</p>		<p> For example:</p>
	<p class="code">RESET MODEL 2		<p class="code">RESET MODEL 2
Line 2,559:		Line 2,559:
	</td></tr>		</td></tr>

	<tr><th>Response</th> <td>Turn off the Janus or TN3270 Debugger, then ~~re-issue~~ the SPY ON command.		<tr><th>Response</th> <td>Turn off the Janus or TN3270 Debugger, then reissue the SPY ON command.
	<p>For example:</p>		<p>For example:</p>
	<p class="code">TN3270 DEBUG OFF		<p class="code">TN3270 DEBUG OFF
	SPY ON</p>		SPY ON</p>
			</td></tr></table>

			----

			<table class="message"><tr><th>Number</th> <td>207</td></tr>

			<tr><th>Type</th> <td>Error.</td></tr>

			<tr><th>Text</th> <td>SoftSpy may not be used in a DBCS environment.</td></tr>

			<tr><th>Description</th> <td>SoftSpy is not supported in a DBCS (double-byte character set) environment.</td></tr>

			<tr><th>Response</th> <td>Ensure that the CCAIN parameter <var>DBCSENV=0</var>, then reissue the SPY command.

	</td></tr></table>		</td></tr></table>

	[[Category: SoftSpy]]		[[Category: SoftSpy]]

JAL: heading caps

2015-08-03T19:01:42Z

heading caps

← Older revision		Revision as of 19:01, 3 August 2015
Line 3:		Line 3:
	This topic contains information on all messages issued by SoftSpy.		This topic contains information on all messages issued by SoftSpy.

	===Terminal ~~Message Format~~===		===Terminal message format===
	Most SoftSpy messages are displayed on the user's terminal. A few are issued to the audit trail.		Most SoftSpy messages are displayed on the user's terminal. A few are issued to the audit trail.

Line 18:		Line 18:
	given in this topic. The messages are documented in numerical order. A gap in the numeric sequence indicates an unused message number.		given in this topic. The messages are documented in numerical order. A gap in the numeric sequence indicates an unused message number.

	===Message ~~Documentation Format~~===		===Message documentation format===
	SoftSpy messages are documented in the following format:		SoftSpy messages are documented in the following format:
	<table>		<table class="thJustBold">
	<tr><th nowrap>Message Number</th> <td>The number of the SoftSpy message.</td></tr>		<tr><th nowrap>Message Number</th> <td>The number of the SoftSpy message.</td></tr>
	<tr><th>Message Type</th> <td>The message type is either Bug, Error, Informational, or Warning.</td></tr>		<tr><th>Message Type</th> <td>The message type is either Bug, Error, Informational, or Warning.</td></tr>

	<tr><th>Message Text</th> <td>The text of the message as it appears on the user's terminal, except for generic terms, such as a keyword, for which SoftSpy substitutes the appropriate value.</td></tr>		<tr><th>Message Text</th> <td>The text of the message as it appears on the user's terminal, except for generic terms, such as a keyword, for which SoftSpy substitutes the appropriate value.</td></tr>

	<tr><th>Description</th> <td>A description of the SoftSpy message. While some descriptions are easily understood, others are longer and more complex, identifying several distinct causes of the message.</td></tr>		<tr><th>Description</th> <td>A description of the SoftSpy message. While some descriptions are easily understood, others are longer and more complex, identifying several distinct causes of the message.</td></tr>

	<tr><th>Response</th> <td>The required response, an indication to notify the SoftSpy Administrator, or an indication that no response is required.</td></tr>		<tr><th>Response</th> <td>The required response, an indication to notify the SoftSpy Administrator, or an indication that no response is required.</td></tr>

	<tr><th>Administrator</th> <td>The required response, if any, for the SoftSpy Administrator.</td></tr>		<tr><th>Administrator</th> <td>The required response, if any, for the SoftSpy Administrator.</td></tr>
	</table>		</table>
Line 31:		Line 35:
	==Messages==		==Messages==
	This topic lists the SoftSpy error messages and responses. A gap in the message number sequence indicates unused message numbers.		This topic lists the SoftSpy error messages and responses. A gap in the message number sequence indicates unused message numbers.

	===Messages 1-25===		===Messages 1-25===
	<table class="message"><tr><th>Number</th> <td> 1</td></tr>		<table class="message">
			<tr><th>Number</th> <td> 1</td></tr>

	<tr><th>Type</th> <td>Error</td></tr>		<tr><th>Type</th> <td>Error</td></tr>
Line 55:		Line 61:
	</table>		</table>
	----		----
	<table class="message"><tr><th>Number</th> <td> 3</td></tr>		<table class="message">
			<tr><th>Number</th> <td> 3</td></tr>

	<tr><th>Type</th> <td>Informational.</td></tr>		<tr><th>Type</th> <td>Informational.</td></tr>
Line 66:		Line 73:
	</table>		</table>
	----		----
	<table class="message"><tr><th>Number</th> <td> 4</td></tr>		<table class="message">
			<tr><th>Number</th> <td> 4</td></tr>

	<tr><th>Type</th> <td>Error.</td></tr>		<tr><th>Type</th> <td>Error.</td></tr>
Line 78:		Line 86:
	----		----

	<table class="message"><tr><th>Number</th> <td> 5</td></tr>		<table class="message">
			<tr><th>Number</th> <td> 5</td></tr>

	<tr><th>Type</th> <td>Informational.</td></tr>		<tr><th>Type</th> <td>Informational.</td></tr>
Line 90:		Line 99:
	----		----

	<table class="message"><tr><th>Number</th> <td> 6</td></tr>		<table class="message">
			<tr><th>Number</th> <td> 6</td></tr>

	<tr><th>Type</th> <td>Error.</td></tr>		<tr><th>Type</th> <td>Error.</td></tr>
Line 102:		Line 112:
	----		----

	<table class="message"><tr><th>Number</th> <td> 7</td></tr>		<table class="message">
			<tr><th>Number</th> <td> 7</td></tr>

	<tr><th>Type</th> <td>Error.</td></tr>		<tr><th>Type</th> <td>Error.</td></tr>

JAL: fix caps for the "official" Debugger product names

2015-04-15T21:05:04Z

fix caps for the "official" Debugger product names

← Older revision		Revision as of 21:05, 15 April 2015
Line 2,543:		Line 2,543:
	<tr><th>Type</th> <td>Error.</td></tr>		<tr><th>Type</th> <td>Error.</td></tr>

	<tr><th>Text</th> <td>SoftSpy may not be used if the ~~JANUS~~/~~tn3270 debugger~~ is on.</td></tr>		<tr><th>Text</th> <td>SoftSpy may not be used if the Janus/TN3270 Debugger is on.</td></tr>

	<tr><th>Description</th> <td>If the ~~JANUS~~ or ~~tn3270 debugger~~ is turned on, any attempt to turn on SoftSpy will be rejected.		<tr><th>Description</th> <td>If the Janus or TN3270 Debugger is turned on, any attempt to turn on SoftSpy will be rejected.
	</td></tr>		</td></tr>

	<tr><th>Response</th> <td>Turn off the ~~JANUS~~ or ~~tn3270 debugger~~, then re-issue the SPY ON command.		<tr><th>Response</th> <td>Turn off the Janus or TN3270 Debugger, then re-issue the SPY ON command.
	<p>For example:</p>		<p>For example:</p>
	<p class="code">TN3270 DEBUG OFF		<p class="code">TN3270 DEBUG OFF

ELowell: /* Messages 176-206 */

2015-04-15T18:30:02Z

Messages 176-206

← Older revision		Revision as of 18:30, 15 April 2015
Line 2,527:		Line 2,527:
	<tr><th>Text</th> <td>SoftSpy may not be used on Model=6 terminals.</td></tr>		<tr><th>Text</th> <td>SoftSpy may not be used on Model=6 terminals.</td></tr>

	<tr><th>Description</th> <td>SoftSpy cannot be used on a "Model 6" terminal (Model 6 terminals are a Sirius Mods extension). Any attempt to use SoftSpy with Model 6 support will be rejected.		<tr><th>Description</th> <td>SoftSpy cannot be used on a "Model 6" terminal (Model 6 terminals are a [[Sirius Mods]] extension). Any attempt to use SoftSpy with Model 6 support will be rejected.
	</td></tr>		</td></tr>

ELowell: /* Messages 176-206 */

2015-04-15T18:27:43Z

Messages 176-206

← Older revision		Revision as of 18:27, 15 April 2015
Line 2,543:		Line 2,543:
	<tr><th>Type</th> <td>Error.</td></tr>		<tr><th>Type</th> <td>Error.</td></tr>

	<tr><th>Text</th> <td>SoftSpy may not be used if the JANUS/~~SIRIUS~~ debugger is on.</td></tr>		<tr><th>Text</th> <td>SoftSpy may not be used if the JANUS/tn3270 debugger is on.</td></tr>

	<tr><th>Description</th> <td>If the JANUS or ~~SIRIUS/TN3270~~ debugger is turned on, any attempt to turn on SoftSpy will be rejected.		<tr><th>Description</th> <td>If the JANUS or tn3270 debugger is turned on, any attempt to turn on SoftSpy will be rejected.
	</td></tr>		</td></tr>

	<tr><th>Response</th> <td>Turn off the ~~SIRIUS~~ or ~~JANUS~~ debugger, then re-issue the SPY ON command.		<tr><th>Response</th> <td>Turn off the JANUS or tn3270 debugger, then re-issue the SPY ON command.
	<p>For example:</p>		<p>For example:</p>
	<p class="code">~~SIRIUS~~ DEBUG OFF		<p class="code">TN3270 DEBUG OFF
	SPY ON</p>		SPY ON</p>
	</td></tr></table>		</td></tr></table>

	[[Category: SoftSpy]]		[[Category: SoftSpy]]

JAL at 20:09, 25 August 2014

2014-08-25T20:09:39Z

← Older revision		Revision as of 20:09, 25 August 2014
Line 737:		Line 737:
	<tr><th>Description</th> <td>An operand type has been used that is not valid in the current context.</td></tr>		<tr><th>Description</th> <td>An operand type has been used that is not valid in the current context.</td></tr>

	<tr><th>Response</th> <td>Refer to ~~the <var class="book">Rocket~~ SoftSpy ~~for Model 204 Reference Manual</var>~~ for an explanation of the available operand types and their syntax. Correct the command syntax and retry.</td></tr></table>		<tr><th>Response</th> <td>Refer to [[SoftSpy operands]] for an explanation of the available operand types and their syntax. Correct the command syntax and retry.</td></tr></table>

	----		----
Line 951:		Line 951:

	<tr><th>Response</th> <td>User partial and final statistics may be displayed by SoftSpy by enclosing the following four terms within parentheses: EVAL (default), LOGIN, STMT, or SPY.		<tr><th>Response</th> <td>User partial and final statistics may be displayed by SoftSpy by enclosing the following four terms within parentheses: EVAL (default), LOGIN, STMT, or SPY.
	<p>For a detailed explanation of this topic, refer to the statistic operand section of ~~the <var class="book">Rocket~~ SoftSpy ~~for Model 204 Reference Manual</var>~~.</p>		<p>
	<p>Correct the command syntax and retry.</p></td></tr></table>		For a detailed explanation of this topic, refer to the statistic operand section of [[SoftSpy operands]].</p>
			<p>
			Correct the command syntax and retry.</p></td></tr></table>

	----		----
Line 965:		Line 967:

	<tr><th>Response</th> <td>Two different types of statistic can be specified: normal Model 204 user statistics and current usage of server table.		<tr><th>Response</th> <td>Two different types of statistic can be specified: normal Model 204 user statistics and current usage of server table.
	<p>For a detailed explanation of this topic, refer to the statistic operand section of ~~the <var class="book">Rocket~~ SoftSpy ~~for Model 204 Reference Manual</var>~~.</p>		<p>For a detailed explanation of this topic, refer to the statistic operand section of [[SoftSpy operands]].</p>
	<p>Correct the command syntax and retry.</p></td></tr></table>		<p>Correct the command syntax and retry.</p></td></tr></table>

Line 1,111:		Line 1,113:
	<tr><th>Description</th> <td>If an operand does not begin with an alphabetic character, or it contains any non-alphanumeric character, then the operand must be enclosed in quotes. The operand must be prefaced with a type indicator unless it is to be treated as a literal string.</td></tr>		<tr><th>Description</th> <td>If an operand does not begin with an alphabetic character, or it contains any non-alphanumeric character, then the operand must be enclosed in quotes. The operand must be prefaced with a type indicator unless it is to be treated as a literal string.</td></tr>

	<tr><th>Response</th> <td>Refer to ~~the <var class="book">Rocket~~ SoftSpy ~~for Model 204 Reference Manual</var>~~ for an explanation of the available operand types and their syntax. <p>Correct the command syntax and retry.</p></td></tr></table>		<tr><th>Response</th> <td>Refer to [[SoftSpy operands]] for an explanation of the available operand types and their syntax.
			<p>Correct the command syntax and retry.</p></td></tr>
			</table>

	----		----
Line 1,255:		Line 1,259:
	<tr><th>Text</th> <td>Invalid SPY command syntax.</td></tr>		<tr><th>Text</th> <td>Invalid SPY command syntax.</td></tr>

	<tr><th>Description</th> <td>A SPY command has been issued with an invalid parameter. <p>Refer to ~~the <var class="book">Rocket~~ SoftSpy ~~for Model 204 Reference Manual</var>~~ for a detailed explanation of the SPY command.</p></td></tr>		<tr><th>Description</th> <td>A SPY command has been issued with an invalid parameter.
			<p>Refer to [[SoftSpy commands and macros]] for a detailed explanation of the SPY command.</p></td></tr>

	<tr><th>Response</th> <td>Correct the command syntax and retry.</td></tr></table>		<tr><th>Response</th> <td>Correct the command syntax and retry.</td></tr></table>
Line 1,269:		Line 1,274:
	<tr><th>Description</th> <td>An OPEN WINDOW command has been issued without the required ROW and/or COLUMN parameters specifying the placement of the window on the screen. These parameters would be optional if they had been previously specified in the DEFINE WINDOW command.		<tr><th>Description</th> <td>An OPEN WINDOW command has been issued without the required ROW and/or COLUMN parameters specifying the placement of the window on the screen. These parameters would be optional if they had been previously specified in the DEFINE WINDOW command.

	<p>For a more detailed explanation of this topic, refer to ~~the~~ OPEN WINDOW ~~section of the <var class="term">Rocket SoftSpy for Model 204 Reference Manual</var>~~.</p></td></tr>		<p>For a more detailed explanation of this topic, refer to [[SoftSpy commands and macros#OPEN WINDOW\|OPEN WINDOW]].</p></td></tr>

	<tr><th>Response</th> <td>Reissue the command with the missing placement parameters.</td></tr></table>		<tr><th>Response</th> <td>Reissue the command with the missing placement parameters.</td></tr></table>
Line 1,960:		Line 1,965:
	<tr><th>Description</th> <td>An invalid <var class="term">compilation_operand</var> has been requested.</td></tr>		<tr><th>Description</th> <td>An invalid <var class="term">compilation_operand</var> has been requested.</td></tr>

	<tr><th>Response</th> <td>For a detailed explanation of this topic, refer to the compilation operand section of ~~the <var class="book">~~SoftSpy ~~Reference Manual</var>~~. <p>Correct the command syntax and retry.</p></td></tr></table>		<tr><th>Response</th> <td>For a detailed explanation of this topic, refer to the compilation operand section of [[SoftSpy operands]].
			<p>Correct the command syntax and retry.</p></td></tr>
			</table>

	----		----
Line 1,972:		Line 1,979:
	<tr><th>Description</th> <td>An invalid <var class="term">quality_assurance_operand</var> has been requested.</td></tr>		<tr><th>Description</th> <td>An invalid <var class="term">quality_assurance_operand</var> has been requested.</td></tr>

	<tr><th>Response</th> <td>For a detailed explanation of this topic, refer to the quality assurance operand section of ~~the <var class="term">~~SoftSpy ~~Reference Manual</var>~~.		<tr><th>Response</th> <td>For a detailed explanation of this topic, refer to the quality assurance operand section of [[SoftSpy operands]].
			<p>
	<p>Correct the command syntax and retry.</p></td></tr></table>		Correct the command syntax and retry.</p></td></tr>
			</table>

	----		----

ELowell: /* Messages 176-206 */

2014-04-15T15:59:30Z

Messages 176-206

← Older revision		Revision as of 15:59, 15 April 2014
Line 2,456:		Line 2,456:
	<tr><th>Text</th> <td>Subscript too high for pre-allocated field <var class="term">fieldname</var>.</td></tr>		<tr><th>Text</th> <td>Subscript too high for pre-allocated field <var class="term">fieldname</var>.</td></tr>

	<tr><th>Description</th> <td>The SET command was used to update a ~~pre-allocated~~ field and the subscript provided was greater than the number of occurrences defined for the field.</td></tr>		<tr><th>Description</th> <td>The SET command was used to update a preallocated field and the subscript provided was greater than the number of occurrences defined for the field.</td></tr>

	<tr><th>Response</th> <td>Correct the command and retry.</td></tr></table>		<tr><th>Response</th> <td>Correct the command and retry.</td></tr></table>

ELowell at 21:42, 18 March 2014

2014-03-18T21:42:45Z

← Older revision		Revision as of 21:42, 18 March 2014
Line 2,545:		Line 2,545:
	SPY ON</p>		SPY ON</p>
	</td></tr></table>		</td></tr></table>

			[[Category: SoftSpy]]

ELowell: Created page with " ==Introduction== This topic contains information on all messages issued by SoftSpy. ===Terminal Message Format=== Most SoftSpy messages are displayed on the user's terminal..."

2014-03-18T21:23:21Z

Created page with " ==Introduction== This topic contains information on all messages issued by SoftSpy. ===Terminal Message Format=== Most SoftSpy messages are displayed on the user's terminal..."

Show changes

← Older revision		Revision as of 23:24, 13 April 2017
Line 159:		Line 159:
	<tr><th>Response</th> <td>Wait until a current SoftSpy user issues a SPY OFF command and then reissue the SPY ON command, or log on to a different Model 204 thread which has an output page buffer size that matches a currently available SoftSpy server. Alternatively, request that your SoftSpy administrator increase the number of SoftSpy servers.</td></tr>		<tr><th>Response</th> <td>Wait until a current SoftSpy user issues a SPY OFF command and then reissue the SPY ON command, or log on to a different Model 204 thread which has an output page buffer size that matches a currently available SoftSpy server. Alternatively, request that your SoftSpy administrator increase the number of SoftSpy servers.</td></tr>

	<tr><th>Administrator</th> <td>Increase the number of SoftSpy servers if warranted. The installation guide contains information on how to define IODEV=55 threads for SoftSpy servers for future active jobs.		<tr><th>Administrator</th> <td>Increase the number of SoftSpy servers if warranted. The [[SoftSpy installation guide]] contains information on how to define IODEV=55 threads for SoftSpy servers for future active jobs.

	<p>Additional SoftSpy servers can be created within the current online job by issuing the SPY SERVER command from a Model 204 terminal session. However, that terminal session will not be available for any other use until the online is brought down.</p></td></tr>		<p>Additional SoftSpy servers can be created within the current online job by issuing the SPY SERVER command from a Model 204 terminal session. However, that terminal session will not be available for any other use until the online is brought down.</p></td></tr>
Line 175:		Line 175:

	<tr><th>Response</th> <td>Contact your SoftSpy administrator.</td></tr>		<tr><th>Response</th> <td>Contact your SoftSpy administrator.</td></tr>
	<tr><th>Administrator</th> <td>If no IODEV=55 threads are included in the CCAIN input stream, they must be added. The installation guide contains information on how to define IODEV=55 threads for SoftSpy servers.		<tr><th>Administrator</th> <td>If no IODEV=55 threads are included in the CCAIN input stream, they must be added. The [[SoftSpy installation guide]] contains information on how to define IODEV=55 threads for SoftSpy servers.

	<p>If IODEV=55 threads are defined, issue the SPY EDIT CONFIG command. Press PF 8 (Forward), and examine the configuration. If the current date is after the expiration date, or the configuration specifies a start date that is after the current date, then contact Technical Support for a key with new dates. If the CPU model and serial number do not match your processor, contact Technical Support with your current CPU model and serial number for a new key. </p>		<p>If IODEV=55 threads are defined, issue the SPY EDIT CONFIG command. Press PF 8 (Forward), and examine the configuration. If the current date is after the expiration date, or the configuration specifies a start date that is after the current date, then contact Technical Support for a key with new dates. If the CPU model and serial number do not match your processor, contact Technical Support with your current CPU model and serial number for a new key. </p>
Line 1,544:		Line 1,544:
	<tr><th>Response</th> <td>Use a terminal whose output page buffer size matches that of the SoftSpy servers. Alternatively, request that your SoftSpy administrator create a SoftSpy server.</td></tr>		<tr><th>Response</th> <td>Use a terminal whose output page buffer size matches that of the SoftSpy servers. Alternatively, request that your SoftSpy administrator create a SoftSpy server.</td></tr>

	<tr><th>Administrator</th> <td>The ~~<var class="book">~~SoftSpy ~~Installation Guide</var>~~ contains information on how to define IODEV=55 threads for SoftSpy servers for future active jobs. Additional SoftSpy servers can be created within the current online job by issuing the SPY SERVER command from a Model 204 terminal session whose output page buffer size matches that of the terminal used for the debugging session. However, that terminal session will not be available for any other use until the online is brought down.</td></tr></table>		<tr><th>Administrator</th> <td>The [[SoftSpy installation guide]] contains information on how to define IODEV=55 threads for SoftSpy servers for future active jobs. Additional SoftSpy servers can be created within the current online job by issuing the SPY SERVER command from a Model 204 terminal session whose output page buffer size matches that of the terminal used for the debugging session. However, that terminal session will not be available for any other use until the online is brought down.</td></tr></table>

	----		----
Line 1,558:		Line 1,558:
	<tr><th>Response</th> <td>Wait until a current SoftSpy user issues a SPY OFF command and then reissue the SPY ON command, or log on to a different Model 204 thread which has an output page buffer size that matches a currently available SoftSpy server. Alternatively, request that your SoftSpy administrator increase the number of SoftSpy servers.</td></tr>		<tr><th>Response</th> <td>Wait until a current SoftSpy user issues a SPY OFF command and then reissue the SPY ON command, or log on to a different Model 204 thread which has an output page buffer size that matches a currently available SoftSpy server. Alternatively, request that your SoftSpy administrator increase the number of SoftSpy servers.</td></tr>

	<tr><th>Administrator</th> <td>The ~~<var class="book">~~SoftSpy ~~Installation Guide</var>~~ contains information on how to define IODEV=55 threads for SoftSpy servers for future active jobs. Additional SoftSpy servers can also be created within the current online job by issuing the SPY SERVER command from a Model 204 terminal session. However, that terminal session will not be available for any other use until the online is brought down.</td></tr></table>		<tr><th>Administrator</th> <td>The [[SoftSpy installation guide]] contains information on how to define IODEV=55 threads for SoftSpy servers for future active jobs. Additional SoftSpy servers can also be created within the current online job by issuing the SPY SERVER command from a Model 204 terminal session. However, that terminal session will not be available for any other use until the online is brought down.</td></tr></table>

	----		----