CICS interface configuration - Revision history

JAL: add links

2017-04-05T23:12:31Z

add links

← Older revision		Revision as of 23:12, 5 April 2017
Line 225:		Line 225:

	For example, the screen size for a model 2 is 1920 bytes, and <var>LOUTPB</var> can be set at 2000.		For example, the screen size for a model 2 is 1920 bytes, and <var>LOUTPB</var> can be set at 2000.

			==See also==
			<ul>
			<li>[[Model 204 installation on IBM z/OS#Install the CICS interface\|Installing the Model 204 CICS interface on z/OS]] </li>

			<li>[[Model 204 installation on IBM z/VSE#CICS interface installation\|Installing the Model 204 CICS interface on z/VSE]] </li>
			</ul>

	[[Category:Installation]]		[[Category:Installation]]

Admin: Admin moved page CICS interface to CICS interface configuration without leaving a redirect: more precise title

2017-04-04T20:00:54Z

Admin moved page CICS interface to CICS interface configuration without leaving a redirect: more precise title

← Older revision	Revision as of 20:00, 4 April 2017
(No difference)

JAL: minor formatting

2017-04-04T19:35:42Z

minor formatting

← Older revision		Revision as of 19:35, 4 April 2017
Line 101:		Line 101:

	<blockquote class="note">		<blockquote class="note">
	<p><b>Note:</b> If you are using [[Defining the user environment (CCAIN)#CRAM options for z.2FOS\|CRAM XDM]], you can run the above programs in <code>USER</code> key. However, to do so, you must link the CRAM XDM M204X* modules with <code>PARM</code> value <code>RENT</code>. </p>		<p><b>Note:</b> If you are using [[Defining the user environment (CCAIN)#CRAM options for z.2FOS\|CRAM-XDM]], you can run the above programs in <code>USER</code> key. However, to do so, you must link the CRAM-XDM M204X* modules with <code>PARM</code> value <code>RENT</code>. </p>
	<ul>		<ul>
	<li>For Model 204 version 7.5 and above, verify the presence of the <code>RENT</code> value for <code>PARM</code> in the STEPXMOD step in the LKCRAMJ link JCL. In earlier versions, the M204X* modules were not linked <code>RENT</code>.</li>		<li>For Model 204 version 7.5 and above, verify the presence of the <code>RENT</code> value for <code>PARM</code> in the STEPXMOD step in the LKCRAMJ link JCL. In earlier versions, the M204X* modules were not linked <code>RENT</code>.</li>
Line 108:		Line 108:
	</ul>		</ul>
	<p>		<p>
	You will need to recycle the XDM region after bringing down all Model 204 Onlines and CICS regions that use XDM ~~CRAM~~. </p>		You will need to recycle the XDM region after bringing down all Model 204 Onlines and CICS regions that use CRAM-XDM. </p>
	</blockquote>		</blockquote>

JAL: /* Running with storage protection on */ mention no-RENT used pre-7.5

2016-07-05T21:00:19Z

Running with storage protection on: mention no-RENT used pre-7.5

← Older revision		Revision as of 21:00, 5 July 2016
Line 103:		Line 103:
	<p><b>Note:</b> If you are using [[Defining the user environment (CCAIN)#CRAM options for z.2FOS\|CRAM XDM]], you can run the above programs in <code>USER</code> key. However, to do so, you must link the CRAM XDM M204X* modules with <code>PARM</code> value <code>RENT</code>. </p>		<p><b>Note:</b> If you are using [[Defining the user environment (CCAIN)#CRAM options for z.2FOS\|CRAM XDM]], you can run the above programs in <code>USER</code> key. However, to do so, you must link the CRAM XDM M204X* modules with <code>PARM</code> value <code>RENT</code>. </p>
	<ul>		<ul>
	<li>For Model 204 version 7.5 and above, ~~check for~~ the <code>RENT</code> value for <code>PARM</code> in the STEPXMOD step in the LKCRAMJ link JCL. </li>		<li>For Model 204 version 7.5 and above, verify the presence of the <code>RENT</code> value for <code>PARM</code> in the STEPXMOD step in the LKCRAMJ link JCL. In earlier versions, the M204X* modules were not linked <code>RENT</code>.</li>

	<li>For version 7.4 and below, relink M204XCRM using the LINKXCRM JCL in your JCL library with <code>PARM</code> value <code>RENT</code>. </li>		<li>For version 7.4 and below, relink M204XCRM using the LINKXCRM JCL in your JCL library with <code>PARM</code> value <code>RENT</code>. </li>

JAL: /* Use the CICS Standard Mapping Service */ typo

2016-07-01T00:54:41Z

Use the CICS Standard Mapping Service: typo

← Older revision		Revision as of 00:54, 1 July 2016
Line 103:		Line 103:
	<p><b>Note:</b> If you are using [[Defining the user environment (CCAIN)#CRAM options for z.2FOS\|CRAM XDM]], you can run the above programs in <code>USER</code> key. However, to do so, you must link the CRAM XDM M204X* modules with <code>PARM</code> value <code>RENT</code>. </p>		<p><b>Note:</b> If you are using [[Defining the user environment (CCAIN)#CRAM options for z.2FOS\|CRAM XDM]], you can run the above programs in <code>USER</code> key. However, to do so, you must link the CRAM XDM M204X* modules with <code>PARM</code> value <code>RENT</code>. </p>
	<ul>		<ul>
	<li>For Model 204 version 7.5 and above, check for the <code>RENT</code> value for <code>PARM</code> in the STEPXMOD step in the ~~LKCRAMP~~ link JCL. </li>		<li>For Model 204 version 7.5 and above, check for the <code>RENT</code> value for <code>PARM</code> in the STEPXMOD step in the LKCRAMJ link JCL. </li>

	<li>For version 7.4 and below, relink M204XCRM using the LINKXCRM JCL in your JCL library with <code>PARM</code> value <code>RENT</code>. </li>		<li>For version 7.4 and below, relink M204XCRM using the LINKXCRM JCL in your JCL library with <code>PARM</code> value <code>RENT</code>. </li>

JAL: add note re CRAM XDM and CICS

2016-06-30T23:03:46Z

add note re CRAM XDM and CICS

Show changes

ELowell: /* Running with storage protection on */

2016-04-05T16:43:06Z

Running with storage protection on

← Older revision		Revision as of 16:43, 5 April 2016
Line 65:		Line 65:
	==Use the CICS Standard Mapping Service==		==Use the CICS Standard Mapping Service==
	===Running with storage protection on===		===Running with storage protection on===
	If you are running CICS ~~3.3 or later~~ with storage protection on, you must do the		If you are running CICS with storage protection on, you must do the following to avoid ABENDs:
	following to avoid ABENDs:
	<ul>		<ul>
	<li>If you are using the IFAM interface, define the program DFHPSF with		<li>If you are using the IFAM interface, define the program DFHPSF with
Line 77:		Line 76:
	both CICS or both USER.</li>		both CICS or both USER.</li>
	</ul>		</ul>

	===Preventing A03 abends===		===Preventing A03 abends===
	To prevent A03 abends during CICS shutdown, or to control the closing of		To prevent A03 abends during CICS shutdown, or to control the closing of

ELowell: /* Overview of the CICS Interface */

2016-04-05T15:45:20Z

Overview of the CICS Interface

← Older revision		Revision as of 15:45, 5 April 2016
Line 3:		Line 3:
	to Model 204 facilities and support for CICS pseudo conversational programs.		to Model 204 facilities and support for CICS pseudo conversational programs.

	The Model 204 CICS Interface provides CICS users ~~(Release 3.3 and later and~~		The Model 204 CICS Interface provides CICS users with a pseudo conversational version of the fullscreen and IFAM2 (Host Language and Remote User Language) interfaces of
	~~Transaction Server releases)~~ with a pseudo conversational version of the fullscreen
	and IFAM2 (Host Language and Remote User Language) interfaces of
	Model 204. The Model 204 CICS Interface allows no resources to be held by a		Model 204. The Model 204 CICS Interface allows no resources to be held by a
	task during a conversational iteration with the terminal operator.		task during a conversational iteration with the terminal operator.

ELowell: /* CICS interface components */

2014-12-23T19:29:10Z

CICS interface components

← Older revision		Revision as of 19:29, 23 December 2014
Line 54:		Line 54:
	<tr><td>CICFG</td> <td>COPY file</td> <td>Specify installation-specific parameters.</td></tr>		<tr><td>CICFG</td> <td>COPY file</td> <td>Specify installation-specific parameters.</td></tr>
	<tr><td>IFENTPS</td> <td>IFAM2 application program interface module</td> <td>Must be linked with the CICS user program and can be used with either a macro- or command-level version of the CICS Interface. The version is determined by a conditional assemble switch contained in CICFG.</td></tr>		<tr><td>IFENTPS</td> <td>IFAM2 application program interface module</td> <td>Must be linked with the CICS user program and can be used with either a macro- or command-level version of the CICS Interface. The version is determined by a conditional assemble switch contained in CICFG.</td></tr>
	<tr><td>IFIF</td> <td>Supports IFAM2</td> <td /></tr>		<tr><td style=white-space:nowrap>IFIF <br />IFIFDOS (for VSE)</td> <td>Supports IFAM2</td> <td /></tr>
	<tr><td>IFPPCI</td> <td>Interface for process-to-process applications</td> <td>Must be linked with CICS user		<tr><td>IFPPCI</td> <td>Interface for process-to-process applications</td> <td>Must be linked with CICS user
	program.</td></tr>		program.</td></tr>

ELowell: /* Overview of the CICS Interface */

2014-12-23T19:23:26Z

Overview of the CICS Interface

← Older revision		Revision as of 19:23, 23 December 2014
Line 11:		Line 11:
	The following figure illustrates the module configuration for the CICS Interface.		The following figure illustrates the module configuration for the CICS Interface.

	[[File:~~CICS_interface_module_config~~.gif\|border]]		[[File:CICS_interface_with_VSE.gif\|border]]

	<p class="caption" style="margin-right:15em">CICS Interface module configuration</p>		<p class="caption" style="margin-right:15em">CICS Interface module configuration</p>