Updates to IMS Network Compression Facility for z/OS, Version 1.1

Manual


Abstract

Updates that apply to IMS™ Network Compression Facility for z/OS, Version 1.1 User's Guide (SC27-1281-01)

Content

Update 2 Feb 2010 (PM03460)


Add the following paragraph to the end of the description of the PPUE0= keyword on page 7.

If IMS Tools Generic Exits is installed on your IMS system, IMS Network
CF ignores any PPUE0= statements and writes a
warning message to the MVS system log. Use IMS Tools Generic Exits
features instead of the PPUE0= keyword to drive other Partner
Product Initialization exit routines. See "Compatibility with IMS
Tools Generic Exits" for more information.


Add a new section to the end of Chapter 2, Customization.

Compatibility with IMS Tools Generic Exits
==========================================

Some IMS Tools include a feature called IMS Tools Generic Exits.
This is a separate FMID (H32A130) that includes a means to drive
other products exits, including the Partner Product Initialization
exit (DFSPPUE0).

If your installation uses IMS Tools Generic Exits, you should
use its features to drive all required DFSPPUE0 exits instead of
the PPUE0= keyword that is provided in IMS Network CF.
When IMS Tools Generic Exits drives the IMS Network CF Partner
exit (DFSPPUE0), IMS Network CF bypasses calling any PPUE0
exits that was specified by using the PPUE0= keyword (as described
in the Keywords section). In addition, IMS Network CF writes a warning message
to the MVS system log that shows the names of each bypassed PPUE0
exit routine that was specified in the IMS Network CF options.

Because IMS Tools Generic Exits and IMS Network CF
include an IMS Partner Product Initialization exit routine
(module DFSPPUE0), IMS Network CF includes a usermod to
remove the module from the SCFNLOAD library.

If IMS Tools Generic Exits is active in your IMS environment, you
must complete the following steps:

1. Determine if IMS Tools Generic Exits is active.
2. Define the IMS Network CF Partner exit to the IMS Tools
Generic Partner exit.
3. Remove the DFSPPUE0 alias to CFNPPUE0.


1. Determine if IMS Tools Generic Exits is Active
-------------------------------------------------

When the IMS Tools Generic Exits are active, the following message
is issued during the IMS control region initialization.

GPR2926I IMS TOOLS GENERIC PARTNER EXIT INITIALIZATION IN PROGRESS

If your IMS system does not write this message during IMS restart,
ignore the steps in the rest of this topic.


2. Define the IMS Network CF Partner Exit
-------------------------------------------------------

Update the IMS Tools Generic Partner exit PROCLIB member (either
GPREXIT0 or GPRiiii0) to define the IMS Network CF
Partner exit, CFNPPUE0. You must add a statement, as shown in the
following example:

EXITDEF(TYPE(PARTNER)
EXITNAME(CFNPPUE0)
LOADLIB(hlq.SCFNLOAD)
)

See the "IMS Tools Common Services Reference," SC19-2546,
for details on defining Generic Partner exit routines.


3. Remove the DFSPPUE0 alias to CFNPPUE0
----------------------------------------

Install IMS Network CF usermod number 1 to remove the DFSPPUE0 alias.
The usermod can be found in the SCFNSAMP library in member CFNUM01.

Sample jobs to receive, apply, and accept this usermod can also be
found in the SCFNSAMP library. Run the three jobs
below to install the usermod. All jobs must receive condition
code 0000.

SCFNSAMP
Member Purpose
-------- --------------------------------------------
CFN1RECV Receive the usermod.
CFN1APLY Apply the usermod to the target zone.
CFN1ACPT Accept the usermod to the distribution zone.

Normally, usermods are not to be accepted. But this usermod
does not update any code, it only removes the DFSPPUE0 alias
from the SCFNLOAD library and updates JCLIN to remove the alias
from any updates that may relink CFNPPUE0 in future PTFs.

Important: If you apply this usermod, the SMP RESTORE command can be
used to restore the usermod, but SMP does not recreate the
DFSPPUE0 alias that was deleted when the usermod was applied. If
you have installed the usermod, but decide that you do not want
this function, you can install usermod CFNUM02 to recreate
the DFSPPUE0 alias and place the alias back in the JCLIN.
Sample jobs to receive CFNUM02 (in member CFN2RECV), apply
CFNUM02 (in member CFN2APLY), and accept CFNUM02 (in member
CFN2ACPT) are in the SCFNSAMP library.



Add message:

CFN1047W IMS NCF DETECTED GENERIC EXITS-BYPASSING EXIT exitname

Explanation: IMS Network CF detected that the Generic
Partner Exit was in use. Because Generic Partner Exit provides the
facility to call all required Partner exits (DFSPPUE0 exits), IMS Network CF
does not call the named module, even though the module was requested in a
PPUE0= statement in the CFNPimid member. For additional information
on the Generic Partner Exit, see IMS Tools Common Services Reference,
SC19-2546.

System Action: The specified DFSPPUE0 exit routine is not invoked.

Programmer Response: If you must call the exit routine, add
the exit name to the Generic Partner exit member of the IMS PROCLIB, either
GPREXIT0 or GPRimid0 (where "imid" is the 4 character IMSID).

Module: CFNINITn





Update 1 (July 2006)

The following messages were added to Appendix B. Messages.

CFNA077 SECURITY ERROR

Explanation: A security request was rejected. The long version of this message provides additional information, including the RACF return code and reason code, and the function being performed. The function indicates INITUSER (attempt to establish the TSO user ID in the APPC initiator), AUTH (verify access to the class FACILITY NCF resource profile), or DELUSER (delete the TSO user control blocks in the APPC initiator).

System Action: The request is rejected.

Programmer Response: Review the MVS SYSLOG for an ICH408I or other RACF message that might indicate the reason for the RACF error or security problem.


CFNA078 SECURITY CHECK FAILED

Explanation: A security request was rejected. The long version of this message provides additional information, including the RACF return code and reason code.

System Action: The request is rejected.

Programmer Response: Review the MVS SYSLOG for an ICH408I or other RACF message that indicates the reason RACF denied the authorization request.


CFNA079 SECURITY ERROR

Explanation: The attempt to establish the TSO user's security environment in the APPC initiator address space failed because the user's password was expired or the user ID was not defined on the system where IMS is running. The long version of this message provides additional information, including the RACF return code and reason code, and the reason for the error.

System Action: The request is rejected.

Programmer Response: Review the MVS SYSLOG for an ICH408I or other RACF message that indicates the reason RACF was unable to establish the TSO user ID in the APPC initiator address space.


CFN1164E UNEXPECTED RETURN CODE RECEIVED FROM CSVQUERY-RC

Explanation: The attempt to establish the TSO user's security environment in the APPC initiator address space failed because the user's password was expired or the user ID was not defined on the system where IMS is running. The long version of this message provides additional information, including the RACF return code and reason code, and the reason for the error.

System Action: IMS continues initialization without Network Compression Facility.

Programmer Response: Review the MVS SYSLOG for an ICH408I or other RACF message that indicates the reason RACF was unable to establish the TSO user ID in the APPC initiator address space.


CFN1165W SECOND INVOCATION OF NCF IGNORED

Explanation: CFNPPUE0 (or it's alias DFSPPUE0) was called more than once during the IMS initialization process. NCF ignores the second (and any subsequent) calls.

System Action: Multiple calls to initialize NCF are ignored.

Programmer Response: Review your environment to determine the reason why CFNPPUE0 (or it's alias DFSPPUE0) was called more than once during the IMS initialization process.


CFN1320E RACF xxxxxxxx ERROR-SAF RC=xx RACF RC=xx RACF REASON=xx

Explanation: When a RACF error occurs, NCF writes this message to the MVS SYSLOG to help identify the function that was being performed. A similar message is presented to the TSO user that requested the function.

System Action: A user request was rejected.

Programmer Response: A RACF error was encountered. There should be a RACF message such as an ICH408I before this message that identifies the RACF error encountered.

Related information

IMS Network Compression Facility User's Guide

Publication number

SC27-1281-01

Copyright date

2002

Original publication date

2002/10/25

Rate this page:

(0 users)Average rating

Document information


More support for:

IMS Tools
IMS Network Compression Facility

Software version:

1.1.0

Operating system(s):

z/OS

Software edition:

All Editions

Reference #:

7007953

Modified date:

2010-02-16

Translate my page

Machine Translation

Content navigation