Common User Errors

This Section identifies common errors, their causes, and corrective measures.

1. (FOC263) EXTERNAL FUNCTION OR LOAD MODULE NOT FOUND: IMSX

Explanation:

The Interface load module, member IMSX in the 'prefix.IMS.LOAD' library, must be allocated to ddname STEPLIB or USERLIB. This error is usually caused by improper installation of the IMS/DB Interface. The installation instructions state that module IMSX must be allocated as ddname USERLIB or be concatenated into the allocation for ddname STEPLIB.

Solution:

Either allocate 'prefix.IMS.LOAD' as ddname USERLIB or concatenate it to ddname STEPLIB as described in Installation Instructions.

2. (FOC4213) LOCAL DLI CALL ERROR STATUS FOR SEGMENT xxxxxxxx/AC
   (IMS RETURN CODE AC: HIERARCHICAL ERROR IN SSA)

Explanation:

The Interface issued a call to IMS for the segment named xxxxxxxx, and IMS found an error in the hierarchical structure of the IMS database. There are three possibilities:

• The Master File does not exactly match the hierarchy described in the PCB. Use the PSBGEN source statements to check the PCB against the Master File.
• You are using an alternate view of the database and you have requested data from a segment other than the alternate view segment. FOCUS allows you to use TABLE FILE FILENAME.FIELDNAME for IMS files and generates the corresponding unqualified IMS calls for the appropriate segment. However, if you attempt to retrieve data from segments other than the one that is implied in the TABLE request, FOCUS issues the IMS calls using the alternate view structure. IMS will not interpret the call because you have dynamically altered the Master File and the description no longer exactly matches the PCB.
• You have not included all of the IMS segments from the PCB in the Master File. Each IMS segment to be retrieved must be defined in the Master File in the proper order.

Solution:

• Do not use alternate views when using an IMS database.
• Correct any errors in the Master File.

3. (FOC4213) LOCAL DLI CALL ERROR STATUS FOR SEGMENT xxxxxxxx/AD
   (IMS RETURN CODE AD: INVALID PCB USED IN REQUEST EXECUTION)

Explanation:

The Interface used an invalid PCB in a call to IMS. This error occurs when the FOCPSB does not account for the CMPAT parameter in the PSB. Either of the following may be the cause:

• The request used a terminal PCB when it should have used a DB PCB.
• The request used a DB PCB when it should have used a terminal PCB.

Solution:

• If the PSB contains the parameter CMPAT=YES, insert an additional TERM PCB in the FOCPSB (see Chapter 3, Creating FOCUS Descriptions).
• If the PSB does not contain the CMPAT=YES parameter, be sure there is no extra TERM PCB in the FOCPSB.

4. (FOC4213) LOCAL DLI CALL ERROR STATUS FOR SEGMENT xxxxxxxx/AI
   (IMS RETURN CODE AI: DATABASE OPEN ERROR)

Explanation:

The Interface issued a call to IMS for the segment named xxxxxxxx and IMS was unable to open the database. There are three possibilities:

• The ddname does not match the name specified in the DBD.
• The database requested is an offline database and it was not allocated in your CLIST, batch JCL, or from within your session.
• You are attempting to access an online database in BMP mode and it was not allocated in the IMS message region.
• The DBD and PSB are out of synch.

Solution:

a. Allocate the correct ddname in your JCL, CLIST, or from within your session.

b. Check your execution mode. If you are running in DLI (batch) mode, allocate the database in your CLIST, batch JCL, or from within your session. If you are trying to report from an online database, see your System Support Group to allocate the database in the IMS region. Be certain that all datasets in the database are allocated. A good source for the allocations required for offline databases is the JCL used for another application program that accesses the database.

c. Use the ACB instead of the PSB by executing DFSRRC00 with a PARM of DBB rather than DLI (see Environments). Notify your IMS systems programmer.

5. (FOC4213) LOCAL DLI CALL ERROR STATUS FOR SEGMENT xxxxxxxx/AJ
   (IMS RETURN CODE AJ: INVALID PARAMETER FORMAT IN I/O AREA)

Explanation:

Possible problem in Master File.

Solution:

a. Check that the Master File does not define a GROUP within a GROUP.

b. If a GROUP is defined as a key or secondary index, check that the keyword ALIAS is specified explicitly in the Master File and that the ALIAS value includes the correct suffix if the GROUP field is a sequence field, search field, or secondary index (see Chapter 3, Creating FOCUS Descriptions).

c. Verify the segment layout and the sequence and search fields against the DBD.

6. (FOC4213) LOCAL DLI CALL ERROR STATUS FOR SEGMENT xxxxxxxx/AK
   (IMS RETURN CODE AK: INVALID FIELD NAME IN CALL)

Explanation:

The Interface issued a call to IMS in order to retrieve the segment named xxxxxxxx, and IMS does not understand the segment names or the fieldnames in the call.

The names of the segments, fields, and keys in the Master File do not match the names in the IMS DBD. There are three possibilities:

• The segment names in the Master File do not exactly match the SEGM statements (segment names) in the IMS DBD.
• An ALIAS value in the Master File includes the .KEY or .HKY suffix, but either the fieldname does not exist in the DBD, the fieldname does exist in the DBD but it is not designated as the IMS key field (SEQ,U or SEQ,M), or the ALIAS value does not match the name in the DBD.
• An ALIAS in the Master File includes the .IMS suffix, but the exact field name does not appear in the DBD.

Note that IMS search fields must be defined in the DBD.

Solution:

a. Remove the .IMS from any field that is not mentioned in the DBD.

b. Remove the .KEY designation from those fields that are not key fields, or correct the spelling of the ALIAS value.

c. Correct all segment names in the Master File to match the DBD SEGM names.

7. USER ABEND 100 IN AN IMS XMI REGION

Explanation:

This abend results when ddname FOCBMP is not part of the IMS XMI JCL, or the dataset that is allocated to ddname FOCBMP is not catalogued.

Solution:

Correct the error and resubmit the job.

8. (FOC000) ERROR MESSAGE TEXT MISSING: nnnn

Explanation:

Error message number nnnn could not be found in the datasets allocated to ddname ERRORS. The Interface error messages may not have been copied to the error message dataset, as described in Installation Instructions.

Solution:

Either copy the error messages as described in Installation Instructions, or concatenate 'prefix.IMS.DATA' in your allocation for ddname ERRORS (prefix is the high-level qualifier for your FOCUS production libraries).