M204.1521 - Revision history

JAL: remove 0 from token0

2018-03-26T19:49:17Z

remove 0 from token0

← Older revision		Revision as of 19:49, 26 March 2018
Line 1:		Line 1:
	{{Template:M204.1521 skeleton}}		{{Template:M204.1521 skeleton}}
	<P>		<P>
	The <var class="term">~~token0~~</var> entity can be the name of a stream or the name of a data set (file) or a process. </P>		The <var class="term">token</var> entity can be the name of a stream or the name of a data set (file) or a process. </P>
	<P>		<P>
	Under VS1 or z/OS, the <var class="term">~~token0~~</var> entity has not been allocated, or access to the entity-name has not been authorized by an active external security mechanism. </P>		Under VS1 or z/OS, the <var class="term">token</var> entity has not been allocated, or access to the entity-name has not been authorized by an active external security mechanism. </P>
	<P>		<P>
	Under z/VSE, <var class="term">~~token0~~</var> cannot be opened for one of the following reasons: </P>		Under z/VSE, <var class="term">token</var> cannot be opened for one of the following reasons: </P>
	<ul>		<ul>
	<li>The file name in the <var>OPEN</var> command (for a Model 204 file), the <var>Open Dataset</var> statement in the SOUL program (for an external file), or the <var>USE</var> command (for a sequential output file) is correct. Otherwise, the file		<li>The file name in the <var>OPEN</var> command (for a Model 204 file), the <var>Open Dataset</var> statement in the SOUL program (for an external file), or the <var>USE</var> command (for a sequential output file) is correct. Otherwise, the file

JAL: add `'s`

2018-03-07T23:43:27Z

add <var>'s

DmeWiccan: Automatically generated page update

2018-03-07T15:32:13Z

Automatically generated page update

New page

{{Template:M204.1521 skeleton}}

The <var class="term">token0</var> entity can be the name of a stream or the name of a data set (file) or a process. 

Under VS1 or z/OS, the <var class="term">token0</var> entity has not been allocated, or access to the entity-name has not been authorized by an active external security mechanism. 

Under z/VSE, <var class="term">token0</var> cannot be opened for one of the following reasons: 
<ul>
<li>The file name in the OPEN command (for a Model 204 file), the OPEN DATASET statement in the SOUL program (for an external file), or the USE command (for a sequential output file) is correct. Otherwise, the file
name exceeds seven characters, and no associated DEFINE DATASET command was given before the open. </li>

<li>If the file is a disk file, its DLBL and EXTENT statements are missing from the JCL, and they do not exist in the partition standard label area nor in the system standard label area. </li>

<li>If the named external file is a tape file, its TLBL statement is missing from the JCL, the file name is not in the form (SYSnnn), or there was no DEFINE DATASET command to associate the file name with a symbolic unit
number (SYSnnn). </li>

<li>The symbolic unit specified for the named disk file, tape file, or unit record file is unassigned or invalid. (For a sequential file or external file, ASSIGN is a valid assignment.) </li>

<li>A DEFINE DATASET command is missing for the named stream. </li>
</ul>

Response: Correct the file name in your command or SOUL statement, and retry the request. If the request fails again, contact your system manager. Under z/OS, where an external security mechanism is providing authorization,
verify that you have the authority to use the data set for the request. 

System manager response: Under z/OS, check your JCL to ensure there is a DD statement for the data set and that it has been allocated to a valid device. In addition, ensure the user is authorized to access the data set if an external security interface is in operation. 

Under z/VSE, check your JCL and the standard label areas to ensure that a DLBL and an EXTENT statement (for a disk file) or a TLBL statement exists, and that the symbolic unit number has been properly assigned. In addition,
if a DEFINE DATASET command is required, check to ensure that all its parameters have been entered correctly. 

If this problem persists, contact [[Contacting Rocket Software Technical Support|Technical Support]].

{{Template:M204.1521 footer}}

← Older revision		Revision as of 23:43, 7 March 2018
Line 7:		Line 7:
	Under z/VSE, <var class="term">token0</var> cannot be opened for one of the following reasons: </P>		Under z/VSE, <var class="term">token0</var> cannot be opened for one of the following reasons: </P>
	<ul>		<ul>
	<li>The file name in the OPEN command (for a Model 204 file), the ~~OPEN DATASET~~ statement in the SOUL program (for an external file), or the USE command (for a sequential output file) is correct. Otherwise, the file		<li>The file name in the <var>OPEN</var> command (for a Model 204 file), the <var>Open Dataset</var> statement in the SOUL program (for an external file), or the <var>USE</var> command (for a sequential output file) is correct. Otherwise, the file
	name exceeds seven characters, and no associated DEFINE DATASET command was given before the open. </li>		name exceeds seven characters, and no associated <var>DEFINE DATASET</var> command was given before the open. </li>

	<li>If the file is a disk file, its DLBL and EXTENT statements are missing from the JCL, and they do not exist in the partition standard label area nor in the system standard label area. </li>		<li>If the file is a disk file, its DLBL and EXTENT statements are missing from the JCL, and they do not exist in the partition standard label area nor in the system standard label area. </li>

	<li>If the named external file is a tape file, its TLBL statement is missing from the JCL, the file name is not in the form (SYS<i>nnn</i>), or there was no DEFINE DATASET command to associate the file name with a symbolic unit		<li>If the named external file is a tape file, its TLBL statement is missing from the JCL, the file name is not in the form (SYS<i>nnn</i>), or there was no <var>DEFINE DATASET</var> command to associate the file name with a symbolic unit number (SYS<i>nnn</i>). </li>
	number (SYS<i>nnn</i>). </li>

	<li>The symbolic unit specified for the named disk file, tape file, or unit record file is unassigned or invalid. (For a sequential file or external file, ASSIGN is a valid assignment.) </li>		<li>The symbolic unit specified for the named disk file, tape file, or unit record file is unassigned or invalid. (For a sequential file or external file, ASSIGN is a valid assignment.) </li>

	<li>A DEFINE DATASET command is missing for the named stream. </li>		<li>A <var>DEFINE DATASET</var> command is missing for the named stream. </li>
	</ul>		</ul>
	<p>		<p>
	<b>Response:</b> Correct the file name in your command or SOUL statement, and retry the request. If the request fails again, contact your system manager. Under z/OS, where an external security mechanism is providing authorization,		<b>Response:</b> Correct the file name in your command or SOUL statement, and retry the request. If the request fails again, contact your system manager. Under z/OS, where an external security mechanism is providing authorization, verify that you have the authority to use the data set for the request. </p>
	verify that you have the authority to use the data set for the request. </p>
	<p>		<p>
	<b>System manager response:</b> Under z/OS, check your JCL to ensure there is a DD statement for the data set and that it has been allocated to a valid device. In addition, ensure the user is authorized to access the data set if an external security interface is in operation. </p>		<b>System manager response:</b> Under z/OS, check your JCL to ensure there is a DD statement for the data set and that it has been allocated to a valid device. In addition, ensure the user is authorized to access the data set if an external security interface is in operation. </p>
	<P>		<P>
	Under z/VSE, check your JCL and the standard label areas to ensure that a DLBL and an EXTENT statement (for a disk file) or a TLBL statement exists, and that the symbolic unit number has been properly assigned. In addition,		Under z/VSE, check your JCL and the standard label areas to ensure that a DLBL and an EXTENT statement (for a disk file) or a TLBL statement exists, and that the symbolic unit number has been properly assigned. In addition,
	if a DEFINE DATASET command is required, check to ensure that all its parameters have been entered correctly. </P>		if a <var>DEFINE DATASET</var> command is required, check to ensure that all its parameters have been entered correctly. </P>
	<P>		<P>
	If this problem persists, contact [[Contacting Rocket Software Technical Support\|Technical Support]].		If this problem persists, contact [[Contacting Rocket Software Technical Support\|Technical Support]].

M204.1521 - Revision history

JAL: remove 0 from token0

JAL: add 's

DmeWiccan: Automatically generated page update

JAL: add `'s`