Verifying the customization of FM/CICS
After you have completed the initial installation and customization of FM/CICS, you can perform the following steps to verify your customization. You might need to refer to the File Manager for z/OS User’s Guide and Reference for CICS.
You verify the installation and customization of FM/CICS by logging on to a CICS® system where you plan to run FM/CICS. Before you can do this, you must have customized FM/CICS, your CICS® system, and, if necessary, TCP/IP.
- Log on to the CICS® system where you have implemented FM/CICS, and enter the FM/CICS transaction, FM.
- Enter your user ID and press Enter.
- The FM/CICS logon panel is displayed:
If you specified START=TASK in the parameters in FMN3POPT, or you used (START=TASK) to initiate your FM/CICS session, and a valid port number has been provided, then you will see a logon panel similar to this.
- Enter your password and press Enter.
- Unless using the START=TASK option, the batch job to start the FM/CICS
session will be submitted, and then the FM/CICS Primary Option Menu
should be displayed, as shown in The FM/CICS Primary Option Menu.
- If after submitting the FM/CICS batch job, message FMNCA016 is displayed (Job jobname not
responding), the FM/CICS job may have failed or may be queued. Examine
the job log for further details and possible error messages.
If the job log cannot be found (the FM/CICS job was never started) verify that the FMNRDR DD statement has been properly defined in the CICS® startup JCL and that your system has sufficient initiators. See Updating the CICS startup procedures for further information.
Some of the most common reasons the batch job may have failed or been queued are:- Insufficient authority to access one of the libraries in the FM/CICS procedure. Check the system log for security messages.
- TCP/IP is not active on the CICS® region. Check for TCP/IP error messages in the job log and verify that TCP/IP is active on the CICS® region.
- The CICS® Sockets interface has not been started
- Duplicate job name. Verify if another user may have specified the same job name in the FM/CICS Jobcard input field, or a previous FM/CICS job is still active.
- JCL errors. Check the job log for further information.
Note: The options FM, FI, and FD allow the user to invoke File Manager and FM/IMS from this primary option menu. These options will not appear if you did not customize File Manager Base function security to allow this access. For more information, see Accessing other File Manager functions from the primary option menu. - If after submitting the FM/CICS batch job, message FMNCA016 is displayed (Job jobname not
responding), the FM/CICS job may have failed or may be queued. Examine
the job log for further details and possible error messages.
- Enter VER on the command line to display the release level
and PTF level of FM/CICS and
ADFz Common Components. A panel is displayed similar to this:
Notes:
- FM/CICS is always shown as
not APF authorized
, even if you have made File Manager APF-authorized, as FM/CICS cannot run APF-authorized. - When you first install FM/CICS,
-NONE-
will be shown under each component that you have installed. Subsequently, when you have applied service to FM/CICS, a PTF number will be shown, indicating the PTF level of each component you have installed. If you have not installed a component, that component will not be shown at all.If you have installed the Japanese language component, another line will be displayed indicating the service level of that component.
- FM/CICS is always shown as
- Press the Exit key (PF3) to exit from the VER display.
- Enter
VERCICS
on the command line to display the level and version of the running File Manager batch job and FM/CICS on all connected CICS® regions. A panel is displayed similar to this:Notes:- The version, PTF level, and buffer layout level for the running File Manager batch job, and FM/CICS on all interconnected CICS® regions (if the FMN3LVL program is available on those regions), is displayed.
- The level of the File Manager CICS® component and all FM/CICS programs should be the same, otherwise some functions will fail.
- If more than one interconnected CICS® region is displayed, each region should be at the same level as the running FM/CICS batch job. If the level or version is different, these values will be highlighted in red, indicating a possible error.
- A difference in version or level is likely to be due to maintenance not being applied to all instances of FM/CICS, or the FM/CICS programs not being refreshed in the CICS® region after maintenance was applied.
- If FMN3LVL is not available on a
connected system, the text
LOAD ERROR
condition will be displayed. Ensure that FMN3LVL can be loaded on the connected CICS® region and retry the VERCICS command. - If an entry for an interconnected CICS®
region where FM/CICS has been installed is not
displayed in the list, this indicates one of the following:
- An active connection to the region was not acquired when the VERCICS command was issued.
- The FM/CICS program FMN3CICS could not be linked to and loaded on the connected CICS® region.
- A TD queue has been specified for the CONN option in FMN3POPT and the APPLID of the connected CICS® region has not been added to this queue.
Verify that an active connection to the remote region has been acquired and FMN3CICS is available, then retry the VERCICS command.
- Press the Exit key (PF3) to exit from the VERCICS display.
- Press the Exit key (PF3) twice more to exit from FM/CICS.
You can now complete the installation of FM/CICS by performing the ACCEPT processing. The steps involved are described in the File Manager Program Directory.