Defining the user environment (CCAIN) - Revision history

JDamon: /* Bypassing password prompts */

2019-03-14T22:50:25Z

Bypassing password prompts

← Older revision		Revision as of 22:50, 14 March 2019
Line 2,212:		Line 2,212:

	<ul>		<ul>
	<li> A <code>LOGCTL NP CMS</code> command must be issued.</li>		<li> A <code>LOGCTL NP CMS</code> command must have been issued. The command applies to <i>all</i> CCASTAT users.</li>

	<li> The user ID on ~~the~~ <var>LOGIN</var> or <var>LOGON</var> command must equal the CMS user ID of the CMS virtual machine on which the login originated.		<li> The user ID on any subsequent <var>LOGIN</var> or <var>LOGON</var> command must equal the CMS user ID of the CMS virtual machine from which the login originated.
	<p>		<p>
	If ~~the default~~ user ID is not identical to the CMS user ID, <var class="product">Model 204</var> then prompts for a password, and continues login processing.</p></li>		If that user ID is not identical to the CMS user ID, <var class="product">Model 204</var> then prompts for a password, and continues login processing.</p></li>

	<li> ~~User~~ ID must be located in the password table.		<li> The user ID used in the LOGIN command must be located in the password table.
	<p>		<p>
	If the user ID is not in the password table, <var class="product">Model 204</var> prompts for a password and then rejects the login command. </p></li>		If the user ID is not in the password table, <var class="product">Model 204</var> prompts for a password and then rejects the login command. </p></li>
	</ul>		</ul>
			<b>NOTE:</B> Any LOGIN command <i>without</i> a user ID, will successfully logon as the CMS user ID of the user who issued the LOGIN command, assuming the CMS user ID is found in CCASTAT. Also, no password prompt will be issued.

	==CMS service machine console (ALTIODEV=45, 47)==		==CMS service machine console (ALTIODEV=45, 47)==

Dme: /* Bypassing password prompts */

2019-03-14T12:30:17Z

Bypassing password prompts

← Older revision		Revision as of 12:30, 14 March 2019
Line 2,197:		Line 2,197:
	</ul>		</ul>

	====Bypassing password prompts====		====<b id="cmsNoPasswd"></b>Bypassing password prompts====
	<p>		<p>
	Use the <var>[[LOGCTL command: Modifying user ID entries in the password table\|LOGCTL]]</var> command with the <var>NP</var> option to bypass password prompts:</p>		Use the <var>[[LOGCTL command: Modifying user ID entries in the password table\|LOGCTL]]</var> command with the <var>NP</var> option to bypass password prompts:</p>

JDamon: SYSPRINT & CCAPRINT DDs are not required

2018-07-02T20:27:26Z

SYSPRINT & CCAPRINT DDs are not required

← Older revision		Revision as of 20:27, 2 July 2018
Line 1,005:		Line 1,005:
	//STEPLIB DD DSN=M204.LOADLIB,DISP=SHR		//STEPLIB DD DSN=M204.LOADLIB,DISP=SHR
	// DD DSN=M204.CRAMLIB,DISP=SHR		// DD DSN=M204.CRAMLIB,DISP=SHR
	//CCASNAP DD ~~SYSOUT=A~~		//CCASNAP DD SYSOUT=A
	~~//SYSPRINT DD SYSOUT=A~~
	~~//CCAPRINT DD~~ SYSOUT=A
	/*		/*
	//</p>		</p>
	<p>		<p>
	If CRAM is installed in a separate library, the M204.CRAMLIB concatenation shown above is required.</p>		If CRAM is installed in a separate library, the M204.CRAMLIB concatenation shown above is required.</p>

JAL: /* Two CRAM options */ link repair

2018-06-19T20:31:52Z

Two CRAM options: link repair

← Older revision		Revision as of 20:31, 19 June 2018
Line 762:		Line 762:
	CRAM-XDM uses z/OS cross memory services to move pages from one address space to another in one instruction. All data moves are done using access registers. CRAM-XDM initializes a single cross-memory environment, M204XDM, that is shared among all Model 204 Onlines. The M204XDM job is the master XDM job; it must be submitted separately, <i>before</i> the Online jobs that might use that XDM. </p>		CRAM-XDM uses z/OS cross memory services to move pages from one address space to another in one instruction. All data moves are done using access registers. CRAM-XDM initializes a single cross-memory environment, M204XDM, that is shared among all Model 204 Onlines. The M204XDM job is the master XDM job; it must be submitted separately, <i>before</i> the Online jobs that might use that XDM. </p>
	<p>		<p>
	The XDM address space must be [[#~~Implementing CRAM~~-~~XDM usage for z/OS operating systems~~\|defined as non-swappable]], and it uses a system Linkage Index (LX). It is recommended that you define the address space as non-cancellable, in which case it will always recover from an abend.</p></li>		The XDM address space must be [[#The importance of non-swappability\|defined as non-swappable]], and it uses a system Linkage Index (LX). It is recommended that you define the address space as non-cancellable, in which case it will always recover from an abend.</p></li>
	</ul>		</ul>
	<p>		<p>

ELowell at 22:02, 13 October 2017

2017-10-13T22:02:02Z

← Older revision		Revision as of 22:02, 13 October 2017
Line 524:		Line 524:

	<tr>		<tr>
	<td>~~NSUBTSKS~~</td>		<td>NSUBTKS</td>
	<td>IPADDR</td>		<td>IPADDR</td>
	</tr>		</tr>
Line 548:		Line 548:

	<tr>		<tr>
	<td>~~NSUBTSKS~~ </td>		<td>NSUBTKS </td>
	<td>INMRL</td>		<td>INMRL</td>
	</tr>		</tr>

JAL: link repair

2017-06-05T23:18:24Z

link repair

← Older revision		Revision as of 23:18, 5 June 2017
Line 1,072:		Line 1,072:
	<li>Set the [[#Device types (IODEV settings)\|appropriate CCAIN parameters]], especially <var>IODEV</var>, <var>XMEMOPT</var> (including the X'80' bit), and <var>[[XDMSSN parameter\|XDMSSN]]</var>, bring up the Online(s) with which you want to test this new CRAM version.		<li>Set the [[#Device types (IODEV settings)\|appropriate CCAIN parameters]], especially <var>IODEV</var>, <var>XMEMOPT</var> (including the X'80' bit), and <var>[[XDMSSN parameter\|XDMSSN]]</var>, bring up the Online(s) with which you want to test this new CRAM version.

	<p id="204xsvc" class="note"><b>Note:</b> No <var>XMEMSVC</var> parameter setting for XDM is required in CCAIN. The <code>M204XSVC</code> object module, which is linked by default into the CRAM load library, is <i>not</i> installed as an SVC as may have been the case in earlier versions. An <code>INCLUDE</code> for the <code>M204XSVC</code> module is also added to the Online link-edit job by default as of version 7.5. </p>		<p id="204xsvc" class="note"><b>Note:</b> No <var>XMEMSVC</var> parameter setting for XDM is required in CCAIN. The <code>[[Cross-memory facilities CRAM and M204XSVC#M204XSVC\|M204XSVC]]</code> object module, which is linked by default into the CRAM load library, is <i>not</i> installed as an SVC as may have been the case in earlier versions. An <code>INCLUDE</code> for the <code>M204XSVC</code> module is also added to the Online link-edit job by default as of version 7.5. </p>

	<li>Concatenate the CRAM load library to the Online job, or use the <var>XDMSSN</var> parameter in the job's CCAIN so that the Online locates the XDM region.		<li>Concatenate the CRAM load library to the Online job, or use the <var>XDMSSN</var> parameter in the job's CCAIN so that the Online locates the XDM region.

JAL: add link

2017-05-23T18:32:31Z

add link

← Older revision		Revision as of 18:32, 23 May 2017
Line 764:		Line 764:
	The XDM address space must be [[#Implementing CRAM-XDM usage for z/OS operating systems\|defined as non-swappable]], and it uses a system Linkage Index (LX). It is recommended that you define the address space as non-cancellable, in which case it will always recover from an abend.</p></li>		The XDM address space must be [[#Implementing CRAM-XDM usage for z/OS operating systems\|defined as non-swappable]], and it uses a system Linkage Index (LX). It is recommended that you define the address space as non-cancellable, in which case it will always recover from an abend.</p></li>
	</ul>		</ul>
			<p>
			For additional background information about CRAM and its constituent modules, see [[Cross-memory facilities CRAM and M204XSVC]]. </p>

	====CRAM-XDM performance versus CRAM-SVC====		====CRAM-XDM performance versus CRAM-SVC====

JAL: clarify use of ALETs

2017-05-23T00:38:15Z

clarify use of ALETs

← Older revision		Revision as of 00:38, 23 May 2017
Line 794:		Line 794:
	This lets you support more concurrent connections between multiple Onlines and multiple XDM clients connecting to those Onlines (CICS tasks and batch IFAM tasks).</p>		This lets you support more concurrent connections between multiple Onlines and multiple XDM clients connecting to those Onlines (CICS tasks and batch IFAM tasks).</p>
	<p>		<p>
	For example: With XDM prior to version 7.5, a single CICS region that communicates to 3 Online regions needs ~~3 ALETS~~, one for each Online. With XDM version 7.5 and higher, ~~each~~ CICS region may talk to multiple Onlines ~~using one ALET for each CICS region~~ and ~~one for~~ each Online. So for 3 CICS regions to communicate ~~to 3~~ Online regions, a total of ~~6 ALETS~~ is needed versus ~~9 with~~ XDM version 7.4.</p></td>		For example: With XDM prior to version 7.5, a single CICS region that communicates to three Online regions needs three ALETs, one for each Online. With XDM version 7.5 and higher, a CICS region may use the same ALET to talk to multiple Onlines (and similarly, each Online uses a single, separate ALET to talk to one or more CICS regions). So for three CICS regions to communicate with three Online regions under 7.5 and higher, a total of six ALETs is needed (versus nine ALETs under XDM version 7.4).</p></td>
	</tr>		</tr>
	</table>		</table>

JAL: add hyphens for CRAM-SVC

2017-05-22T19:40:02Z

add hyphens for CRAM-SVC

← Older revision		Revision as of 19:40, 22 May 2017
Line 744:		Line 744:
	====Two CRAM options====		====Two CRAM options====
	<p>		<p>
	On z/OS sites, <var class="product">Model 204</var> supports two CRAM options: CRAM SVC and CRAM-XDM (Cross-Memory Data Mover). [[Model 204 installation on IBM z/OS#CRAM\|CRAM-XDM is the default]], and CRAM SVC is deprecated as of Model 204 version 7.5.</p>		On z/OS sites, <var class="product">Model 204</var> supports two CRAM options: CRAM-SVC and CRAM-XDM (Cross-Memory Data Mover). [[Model 204 installation on IBM z/OS#CRAM\|CRAM-XDM is the default]], and CRAM-SVC is deprecated as of Model 204 version 7.5.</p>
	<p>		<p>
	z/VSE sites support only the CRAM SVC option, and z/VM sites support neither.</p>		z/VSE sites support only the CRAM-SVC option, and z/VM sites support neither.</p>

	<p>		<p>
Line 752:		Line 752:

	<ul>		<ul>
	<li>CRAM SVC		<li>CRAM-SVC
	<p>		<p>
	CRAM SVC is CRAM functionality accomplished with SVC calls. CRAM SVC moves data by copying it first to common storage, posting the other side, and then letting the other side copy it. This method is less efficient than CRAM-XDM, which uses z/OS cross memory services. </p>		CRAM-SVC is CRAM functionality accomplished with SVC calls. CRAM-SVC moves data by copying it first to common storage, posting the other side, and then letting the other side copy it. This method is less efficient than CRAM-XDM, which uses z/OS cross memory services. </p>
	<p>		<p>
	Although earlier CRAM SVC installations continue to work for both z/OS and z/VSE sites, it is deprecated as of version 7.5 of Model 204 and no installation instructions are offered.</p></li>		Although earlier CRAM-SVC installations continue to work for both z/OS and z/VSE sites, it is deprecated as of version 7.5 of Model 204 and no installation instructions are offered.</p></li>

	<li>CRAM-XDM		<li>CRAM-XDM
	<p>		<p>
	CRAM-XDM uses z/OS cross memory services to move pages from one address space to another in one instruction. All data moves are done using access registers. CRAM-XDM initializes a single cross-memory environment, M204XDM, that is shared among all Model 204 Onlines. The M204XDM job is the master XDM job; it must be submitted separately, <i>before</i> the Online jobs that might use that XDM. </p>		CRAM-XDM uses z/OS cross memory services to move pages from one address space to another in one instruction. All data moves are done using access registers. CRAM-XDM initializes a single cross-memory environment, M204XDM, that is shared among all Model 204 Onlines. The M204XDM job is the master XDM job; it must be submitted separately, <i>before</i> the Online jobs that might use that XDM. </p>
	<p>		<p>
	The XDM address space must be [[#Implementing CRAM-XDM usage for z/OS operating systems\|defined as non-swappable]], and it uses a system Linkage Index (LX). It is recommended that you define the address space as non-cancellable, in which case it will always recover from an abend.</p></li>		The XDM address space must be [[#Implementing CRAM-XDM usage for z/OS operating systems\|defined as non-swappable]], and it uses a system Linkage Index (LX). It is recommended that you define the address space as non-cancellable, in which case it will always recover from an abend.</p></li>
	</ul>		</ul>

	====CRAM-XDM performance versus CRAM SVC====		====CRAM-XDM performance versus CRAM-SVC====
	If you use CRAM-XDM, the default CRAM option as of version 7.5 of Model 204, you can expect the following performance enhancements compared to CRAM SVC:		If you use CRAM-XDM, the default CRAM option as of version 7.5 of Model 204, you can expect the following performance enhancements compared to CRAM-SVC:

	<table>		<table>
Line 832:		Line 832:
	<li>X'80' bit included: initializes CRAM-XDM environment </li>		<li>X'80' bit included: initializes CRAM-XDM environment </li>

	<li>X'80' bit <i>not</i> included: initializes CRAM SVC environment		<li>X'80' bit <i>not</i> included: initializes CRAM-SVC environment
	</ul>		</ul>
	<p>		<p>
	CRAM-XDM Onlines are compatible with the CRAM SVC option; both can be used on the same z/OS subsystem. However, a given address space can use only one method. All [[#Communicating with multiple regions of Model 204\|channels]] within the Online address space use either the CRAM-XDM option or the CRAM SVC option, but not both.</p>		CRAM-XDM Onlines are compatible with the CRAM-SVC option; both can be used on the same z/OS subsystem. However, a given address space can use only one method. All [[#Communicating with multiple regions of Model 204\|channels]] within the Online address space use either the CRAM-XDM option or the CRAM-SVC option, but not both.</p>

	====CRAM OPEN processing====		====CRAM OPEN processing====
Line 880:		Line 880:
	</ul><br></li>		</ul><br></li>

	<li>CRAM SVC		<li>CRAM-SVC
	<p>		<p>
	The amount of CSA space necessary for CRAM SVC is equal to the amount of virtual storage shown in the calculation in the following subsection.</p></li>		The amount of CSA space necessary for CRAM-SVC is equal to the amount of virtual storage shown in the calculation in the following subsection.</p></li>
	</ul></li>		</ul></li>

Line 888:		Line 888:
	<p>		<p>
	The following calculation determines the approximate virtual storage requirements for each <var class="product">Model 204</var> Online that has <var>IODEV</var> 11, 23, or 29 threads defined.</p>		The following calculation determines the approximate virtual storage requirements for each <var class="product">Model 204</var> Online that has <var>IODEV</var> 11, 23, or 29 threads defined.</p>
	<p class="note"><b>Note:</b> This same amount of space is also required in CSA if CRAM SVC is used. </p>		<p class="note"><b>Note:</b> This same amount of space is also required in CSA if CRAM-SVC is used. </p>

	<p class="code">Virtual storage requirement = Min(<i>nif</i>,1) * (68 + (<i>nif</i> * (IFAMBS + 100)))		<p class="code">Virtual storage requirement = Min(<i>nif</i>,1) * (68 + (<i>nif</i> * (IFAMBS + 100)))
Line 917:		Line 917:

	====CRAM buffer allocation====		====CRAM buffer allocation====
	<p class="note"><b>Note:</b> The CRAM buffer sizing discussed below applies only if CRAM SVC is being used. CRAM-XDM does not use these buffers. </p>		<p class="note"><b>Note:</b> The CRAM buffer sizing discussed below applies only if CRAM-SVC is being used. CRAM-XDM does not use these buffers. </p>
	<p>		<p>
	For <code>IODEV=29</code>, the size of the CRAM buffer is the maximum of (<var>[[INMRL parameter\|INMRL]]</var>, <var>[[OUTMRL parameter\|OUTMRL]]</var>) + 4. If neither of these parameters is specified on the User 0 parameter line, the default of 256 bytes applies.		For <code>IODEV=29</code>, the size of the CRAM buffer is the maximum of (<var>[[INMRL parameter\|INMRL]]</var>, <var>[[OUTMRL parameter\|OUTMRL]]</var>) + 4. If neither of these parameters is specified on the User 0 parameter line, the default of 256 bytes applies.
Line 977:		Line 977:

	====Debugging CRAM====		====Debugging CRAM====
	The debugging utility for CRAM-XDM is M204XMON, and the debugging utility for CRAM SVC is SNAPCRAM. A SNAPCRAM utility also debugs [[#SNAPCRAM utility for z/VSE\|CRAM under z/VSE]].		The debugging utility for CRAM-XDM is M204XMON, and the debugging utility for CRAM-SVC is SNAPCRAM. A SNAPCRAM utility also debugs [[#SNAPCRAM utility for z/VSE\|CRAM under z/VSE]].

	=====M204XMON=====		=====M204XMON=====
Line 996:		Line 996:
	=====SNAPCRAM=====		=====SNAPCRAM=====
	<p>		<p>
	The SNAPCRAM utility is used to debug CRAM SVC under z/OS.		The SNAPCRAM utility is used to debug CRAM-SVC under z/OS.
	SNAPCRAM prints out the CRAM control blocks in dump format. Sample JCL for running SNAPCRAM is:</p>		SNAPCRAM prints out the CRAM control blocks in dump format. Sample JCL for running SNAPCRAM is:</p>

Line 1,031:		Line 1,031:
	<li>Install CRAM-XDM.		<li>Install CRAM-XDM.
	<p>		<p>
	See the Model 204 installation on z/OS [[Model 204 installation on IBM z/OS#CRAM\|instructions for CRAM]]. That CRAM section also includes ways to configure versions of CRAM and Model 204 that are not the same. For example, you might want to wait to install CRAM-XDM until after you install and test <var class="product">Model 204</var> with an existing production version of CRAM. Or you might be making the recommended transition from CRAM SVC to CRAM-XDM. </p></li>		See the Model 204 installation on z/OS [[Model 204 installation on IBM z/OS#CRAM\|instructions for CRAM]]. That CRAM section also includes ways to configure versions of CRAM and Model 204 that are not the same. For example, you might want to wait to install CRAM-XDM until after you install and test <var class="product">Model 204</var> with an existing production version of CRAM. Or you might be making the recommended transition from CRAM-SVC to CRAM-XDM. </p></li>

	<li>Bring down the Online(s) with which you want to test this new CRAM version. </li>		<li>Bring down the Online(s) with which you want to test this new CRAM version. </li>
Line 1,662:		Line 1,662:
	===CRAM IFSTRT IFAM2 (IODEV=23) requirements===		===CRAM IFSTRT IFAM2 (IODEV=23) requirements===
	<p>		<p>
	[[HLI: Job design factors#IFAM2\|IFAM2]] is a <var class="product">Model 204</var> Host Language Interface (HLI) facility that supports host language calls to a <var class="product">Model 204</var> Online from one or more user-written, host language programs. The host languages supported are COBOL, FORTRAN, PL/I, ASSEMBLER, or C. The user-written programs normally run as separate jobs in other regions or partitions, and they connect through the CRAM SVC or CRAM-XDM to a Model 204 Online for database access. Each user program must be linked with a small interface module (IFIF) to enable communication between the user program and the Model 204 Online region.		[[HLI: Job design factors#IFAM2\|IFAM2]] is a <var class="product">Model 204</var> Host Language Interface (HLI) facility that supports host language calls to a <var class="product">Model 204</var> Online from one or more user-written, host language programs. The host languages supported are COBOL, FORTRAN, PL/I, ASSEMBLER, or C. The user-written programs normally run as separate jobs in other regions or partitions, and they connect through the CRAM-SVC or CRAM-XDM to a Model 204 Online for database access. Each user program must be linked with a small interface module (IFIF) to enable communication between the user program and the Model 204 Online region.
	</p>		</p>
	<p>		<p>

JAL: edit ALET info

2017-05-19T20:41:13Z

edit ALET info

← Older revision		Revision as of 20:41, 19 May 2017
Line 760:		Line 760:
	<li>CRAM-XDM		<li>CRAM-XDM
	<p>		<p>
	CRAM-XDM uses z/OS cross memory services to move pages from one address space to another in one instruction. All data moves are done using access registers. CRAM-XDM initializes a single cross-memory environment, M204XDM, that is shared among all Model 204 Onlines. The M204XDM job is the master XDM job; it must be submitted separately ~~from~~ <i>~~and~~ before</i> the Online jobs that might use that XDM. </p>		CRAM-XDM uses z/OS cross memory services to move pages from one address space to another in one instruction. All data moves are done using access registers. CRAM-XDM initializes a single cross-memory environment, M204XDM, that is shared among all Model 204 Onlines. The M204XDM job is the master XDM job; it must be submitted separately, <i>before</i> the Online jobs that might use that XDM. </p>
	<p>		<p>
	The XDM address space must be [[#Implementing CRAM-XDM usage for z/OS operating systems\|defined as non-swappable]], and it uses a system Linkage Index (LX). It is recommended that you define the address space as non-cancellable, in which case it will always recover from an abend.</p></li>		The XDM address space must be [[#Implementing CRAM-XDM usage for z/OS operating systems\|defined as non-swappable]], and it uses a system Linkage Index (LX). It is recommended that you define the address space as non-cancellable, in which case it will always recover from an abend.</p></li>
Line 794:		Line 794:
	This lets you support more concurrent connections between multiple Onlines and multiple XDM clients connecting to those Onlines (CICS tasks and batch IFAM tasks).</p>		This lets you support more concurrent connections between multiple Onlines and multiple XDM clients connecting to those Onlines (CICS tasks and batch IFAM tasks).</p>
	<p>		<p>
	For example: With XDM prior to version 7.4, a single CICS region that communicates to 3 Online regions needs 3 ALETS, one for each Online . With XDM version 7.5, each CICS region may talk to multiple Onlines using one ALET for each CICS region and one for each ~~online~~. So for 3 CICS regions to communicate to 3 Online regions, a total of 6 ALETS is needed versus 9 with XDM version 7.4.</p></td>		For example: With XDM prior to version 7.5, a single CICS region that communicates to 3 Online regions needs 3 ALETS, one for each Online. With XDM version 7.5 and higher, each CICS region may talk to multiple Onlines using one ALET for each CICS region and one for each Online. So for 3 CICS regions to communicate to 3 Online regions, a total of 6 ALETS is needed versus 9 with XDM version 7.4.</p></td>
	</tr>		</tr>
	</table>		</table>