FMNIA005

DFSMDA dynamic allocation member for database &DBNAME not found in the RESLIB data sets for subsystem &SSID.

Could not find a DFSMDA dynamic allocation member for database &DBNAME in the RESLIB data sets for subsystem &SSID. If the subsystem specified on the dialog entry panel has been defined as dynamic allocation only, the message is displayed on the dialog entry panel. Otherwise, the message is displayed on the Database Data Set Specification panel.

Ask the database administrator for the name of the data set that contains the dynamic allocation members for subsystem &SSID and include this data set name in the list of RESLIB data sets for subsystem &SSID on the DLI Mode Data Sets 1 panel (option 0.6.2). If the RESLIB data set name fields are protected, inform the FM/IMS administrator, and he will add the data set name to the FMN1POPI macro statement for the subsystem, and then re-assemble and link-edit the FM/IMS installation options module. Alternatively, if the subsystem has not been defined as dynamic allocation only, and you know the names of the database data sets that are to be used, you may enter the database data set names on the Database Data Set Specification pane, and press Enter.

FMNIA006

DB data set &DSN dynamic allocation error; DYNALLOC reason code is X'&RSN'.

An attempt to allocate database data set &DSN failed. X'&RSN' is the error reason code that the DYNALLOC macro returned.

For an explanation of the DYNALLOC error reason code, see the z/OS MVS Programming: Authorized Assembler Services Guide. Use this information to determine why the data set could not be allocated.

FMNIA010

Key change ignored - One or more key fields were overtyped. All changes on those lines have been ignored.

The REPL DL/I call does not support the modification of key fields in a segment, so when a key field is overtyped, the Editor ignores the change. The Editor also ignores any other changes made on that line, restoring the line to how it was before it was overtyped.

Check the lines that were overtyped and, when necessary, retype the required changes; this time avoiding overtyping a key field.

FMNIA011

Not VSAM - The DBD specifies VSAM for the access method.

The specified data set is a non-VSAM data set, but the DBD specifies VSAM for the access method, so only VSAM data sets can be specified.

Obtain from the database administrator the correct database data set name.

FMNIA012

Not OSAM - The DBD specifies OSAM for the access method.

The specified data set is a non-OSAM data set, but the DBD specifies OSAM for the access method, so only OSAM data sets can be specified.

Obtain from the database administrator the correct database data set name.

FMNIA013

Assembly of dynamic PSB failed with return code &RC.

The PSBGEN assembly step for the dynamic PSB your batch function was generating, failed with a return code of &RC.

Add the following DD statement to the JCL and rerun the job:
//FMN1PRT1 DD SYSOUT=*
The job output will include the PSBGEN assembly listing. Use the assembly listing to determine the cause of the problem.

FMNIA014

Bind of dynamic PSB failed with return code &RC.

The PSBGEN bind step for the dynamic PSB your batch function was generating, failed with a return code of &RC.

Add the following DD statement to the JCL and rerun the job:
//FMN1PRT2 DD SYSOUT=*
The job output will include the PSBGEN bind listing. Use the bind listing to determine the cause of the problem.

FMNIA015

IMS read failed - An attempt to read an IMS segment has failed. The function has been terminated.

An attempt to retrieve an IMS segment failed. The failure was due to an IMS abend, or to system I/O, or security errors, encountered during the execution of the I/O requests.

See the message issued prior to this message for detailed information on the cause of the failure.

FMNIA016

IMS status code AI - A data management open error occurred.

A DL/I call that FM/IMS issued received a status code of AI, indicating that a data management open error occurred.

Read the AI status code explanation in IMS Utilities Reference: Database and Transaction Manager. Message DFS0730I, when issued, gives the cause of the OPEN failure. Search for this message in either:
  • The job log output from the failed job (if the function is a batch function run in DLI mode);
  • The job log for your TSO/E session (if the function is an online function run in DLI mode);
  • The job log for the control region or DLI/SAS region (if the function is run in BMP mode); or
  • The z/OS system log (batch or online function run in BMP or DLI mode).
For an explanation of the reason codes appearing in message DFS0730I, see the description of this message in IMS Messages and Codes Vol 1.

FMNIA017

Invalid DBD - Member &DBNAME of DBD library &DSN does not contain a valid DBD for database &DBNAME.

FM/IMS requires a DBD for the specified database (&DBNAME). FM/IMS searches user, or administrator, specified DBD libraries for the DBD. Which DBD libraries FM/IMS searches depends on which subsystem you select. The DBD libraries that FM/IMS searches are listed on the PSB and DBD Data Sets panel (option 0.6.7). FM/IMS searches these libraries in the order in which they are listed, and uses the first member it finds with the specified database name (&DBNAME). FM/IMS found member &DBNAME in DBD library &DSN, but cannot use it because it does not contain a valid DBD for database &DBNAME.

Either replace member &DBNAME in DBD library &DSN with a DBD for database &DBNAME, or update the list of DBD libraries on the PSB and DBD data sets panel to only include DBD libraries with valid DBDs. You will only be able to update the list when the DBD libraries for the subsystem are not fixed. When the DBD libraries for the subsystem are fixed, the DBD Data set name panel fields are protected and only the FM/IMS administrator can update the list.

FMNIA018

Invalid PSB - Member &PSBNAME of PSB library &DSN does not contain a valid PSB.

FM/IMS searches user, or administrator, specified PSB libraries for a PSB with the specified name (&PSBNAME). Which PSB libraries FM/IMS searches depends on which subsystem you select. The PSB libraries that FM/IMS searches are listed on the PSB and DBD Data Sets panel (option 0.6.7). FM/IMS searches these libraries in the order in which they are listed, and uses the first member it finds with the specified PSB name (&PSBNAME). FM/IMS found member &PSBNAME in PSB library &DSN, but cannot use it because it does not contain a valid PSB.

Either replace member &PSBNAME in PSB library &DSN with a valid PSB, or update the list of PSB libraries on the PSB and DBD data sets panel to only include PSB libraries with valid PSBs. You will only be able to update the list when the PSB libraries for the subsystem are not fixed. When the PSB libraries for the subsystem are fixed, the PSB Data set name panel fields are protected and only the FM/IMS administrator can update the list.

FMNIA019

Not a loadlib - The data set must be a load library.

Self explanatory.

Specify a load library.

FMNIA020

Edit of an index database is not supported.

The specified database is an index database. FM/IMS does not support the edit of an index as a separate database.

If you just want to view the index database, use the Browse function.

FMNIA021

Template for database not in data set &DSN.

The template library (&DSN) specified in the TPLDSN parameter (on the VIEWIMS call), or allocated to the DD specified in the TPLDD parameter (also on the VIEWIMS call), does not have a template for the database that the batch function is accessing.

Either use option 4.1 to create a template for the database and save it in data set &DSN, or specify a different template library that has a template for the database.

FMNIA023

Not an IMS template/view/criteria set - There is a base template/DB2 template/view/criteria set/unknown object in this member/data set - not an IMS template/view/criteria set as is required.

Self explanatory.

Specify a member or data set that contains the required object.

FMNIA024

No secondary indexes - There are no secondary indexes defined for this database.

You have requested access to the database via a secondary index, but the database does not have any secondary indexes.

Blank out the Secondary index option field.

FMNIA026

IMS access denied - The IMS Initialization Exit has denied you access to the requested IMS resources.

You are not authorized to access the requested IMS resources. The IMS Initialization exit denied you access.

If you believe you should be authorized to access the IMS resources, ask the FM/IMS security administrator for the required access.

FMNIA027

Access denied - The Database Data Set Allocation Exit denied your access to this database data set.

You are not authorized to access this database data set. The Database Data Set Allocation exit denied you access.

If you believe you should be authorized to access this database data set, ask the FM/IMS security administrator for access to it.

FMNIA029

IMS log data set &DSN dynamic allocation error; DYNALLOC reason code=X'&RSN'.

An attempt to allocate IMS log data set &DSN failed. X'&RSN' is the error reason code that the DYNALLOC macro returned.

For an explanation of the DYNALLOC error reason code, see z/OS MVS Programming: Authorized Assembler Services Guide. Use this information to determine why the data set could not be allocated.

FMNIA030

DFSVSAMP data set &DSN dynamic allocation error; DYNALLOC reason code=X'&RSN'.

An attempt to allocate the DFSVSAMP data set &DSN failed. X'&RSN' is the error reason code that the DYNALLOC macro returned.

For an explanation of the DYNALLOC error reason code, see z/OS MVS Programming: Authorized Assembler Services Guide. Use this information to determine why the data set could not be allocated.

FMNIA031

There is a base template/IMS template/DB2 template/view/criteria set/unknown object in &DSN/&DSN(&MBR) - not an IMS template/view/criteria set as is required.

The Print, Extract, Batch Edit, and Batch Browse functions issue this message. When the message is issued by the Print function, the data set &DSN, or data set and member &DSN(&MBR)), are specified in the VIEWDSN and VIEWMEM parameters, or in the VIEWDD DD statement. When the message is issued by the Extract function, the data set &DSN, or data set and member &DSN(&MBR), are specified in the CRITDSN and CRITMEM parameters, or in the CRITDD DD statement. When the message is issued by the Batch Edit or Batch Browse function, the data set &DSN, or data set and member &DSN(&MBR), can be specified in a number of places:
  • If it is an IMS template that is required, the data set &DSN is specified in the TPLDSN parameter on the VIEWIMS call, or in the TPLDD DD statement.
  • If it is a view that is required, the data set &DSN, or data set and member &DSN(&MBR), are specified in either the VIEWDSN and VIEWMEM parameters on the VIEWIMS call, the VIEWDSN and VIEWMEM parameters in the FMNIMSIN input, or the VIEWDD DD statement.

Specify a data set, or a data set and member, that contains the required object.

FMNIA032

Create failed - Create failed because DBDLIB &DSN is not a PDS(E). Use option 4.1 or option 4.4 to update the DBDLIBs specified in the template.

The CT command (Create view/criteria set from template) failed because one of the DBDLIB data sets (&DSN) specified in the template is not a PDS(E).

Use option 4.1, or option 4.4, to correct the DBDLIB library list specified in the template.

FMNIA033

Create failed - Create failed because DBDLIB &DSN is not a load library. Use option 4.1 or option 4.4 to update the DBDLIBs specified in the template.

The CT command (Create view/criteria set from template) failed because one of the DBDLIB data sets (&DSN) specified in the template is not a load library.

Use option 4.1, or option 4.4, to correct the DBDLIB library list specified in the template.

FMNIA034

Create failed - Create failed because DBDLIB &DSN was not found in the catalog. Use option 4.1 or option 4.4 to update the DBDLIBs specified in the template.

The CT command (Create view/criteria set from template) failed because one of the DBDLIB data sets (&DSN) specified in the template was not found in the catalog.

Use option 4.1, or option 4.4, to correct the DBDLIB library list specified in the template.

FMNIA035

Invalid template - Found member &DBNAME in Template library &DSN. Expected it to be a template for database &DBNAME, but it was a base template/DB2 template/view/criteria set/unknown object.

Because you have selected 'New' for View or Criteria usage, the function attempts to create a view, or criteria set, from a template for the specified database (&DBNAME). FM/IMS searches user, or administrator, specified template libraries for the template. Which template libraries FM/IMS searches depends on which subsystem you select. The template libraries that FM/IMS searches are listed on the Template Data Sets panel (option 0.6.8). FM/IMS searches these libraries in the order in which they are specified, and uses the first member it finds with the specified database name (&DBNAME).

FM/IMS found a member with the specified database name, but cannot use it because it is not a template.

Either replace member &DBNAME in the Template library &DSN with a template for database &DBNAME, or update the list of Template libraries on the Template Data Sets panel to only include Template libraries with valid templates. You will only be able to update the list when the Template libraries for the subsystem are not fixed. When the template libraries for the subsystem are fixed, the Template Data Set name panel fields are protected, and only the FM/IMS administrator can update the list.

FMNIA036

RESLIB &DSN allocate error - DYNALLOC rc = X'&RSN'. (RESLIB specified in FMN1POPI macro).

An attempt to allocate RESLIB data set &DSN failed. X'&RSN' is the error reason code that the DYNALLOC macro returned. This message is only issued when a BMP region type is selected. In this case, FM/IMS obtains the RESLIB data set names from the FM/IMS installation options module.

For an explanation of the DYNALLOC error reason code, see the z/OS MVS Programming: Authorized Assembler Services Guide. Use this information to determine why the data set could not be allocated. If the list of RESLIB data sets that the function uses has to be altered, inform the FM/IMS administrator, and he will make the necessary changes to the FMN1POPI macro statement for the subsystem and then reassemble, and link-edit, the installation options module.

FMNIA037

RESLIB &DSN allocate error - DYNALLOC rc = X'&RSN'. (RESLIB specified in option 0.6.2)

An attempt to allocate RESLIB data set &DSN failed. X'&RSN' is the error reason code that the DYNALLOC macro returned. This message is only issued when a DLI region type is selected. In this case, FM/IMS obtains the RESLIB data set names from one of the following:
  • The RESLIB data set name fields on the DLI Mode Data Sets 1 panel (when the function is Edit or Browse).
  • The RESLIB parameters specified in the FMNIMSIN input (when the function is a batch function and the RESLIB parameters are specified in the FMNIMSIN input).
  • The FM/IMS installation options module (when the function is a batch function and the RESLIB parameters are not specified in the FMNIMSIN input).

For an explanation of the DYNALLOC error reason code, see the z/OS MVS Programming: Authorized Assembler Services Guide. Use this information to determine why the data set could not be allocated. If the list of RESLIB data sets that the function uses has to be altered:

  • Modify the RESLIB data set names on the DLI Mode Data Set 1 panel (Edit or Browse function); or
  • Modify the RESLIB parameters in the FMNIMSIN input (batch functions).

FMNIA038

No database PCBs - The PSB cannot be used because it does not have any database PCBs.

You have specified a PSB that does not have any database PCBs. The function can only use PSBs that have database PCBs.

Specify a PSB that has one or more database PCBs.

FMNIA039

No PCBs for database - The PSB does not have any PCBs for database &DBNAME.

You cannot use the specified PSB to access database &DBNAME because the PSB does not have any PCBs for the database.

If you want to access database &DBNAME, specify a PSB that has a PCB for this database.

FMNIA040

View saved - The view has been saved in the specified data set.

Self explanatory.

No action is required.

FMNIA041

View created - View created and saved in the specified view data set.

Self explanatory.

No action is required.

FMNIA043

Invalid options module - Invalid FM/IMS installation options module - no IMS subsystems were found in the module.

Self explanatory.

Report this problem to the FM/IMS administrator.

FMNIA044

No matches - No subsystems in the FM/IMS installation options module match the specified pattern.

You specified a pattern in the IMS Subsystem Name field, and no subsystems specified in the FM/IMS installation options module match this pattern.

For a list of all the subsystems specified in the FM/IMS installation options module, blank out the IMS subsystem name field and press Enter.

FMNIA045

Subsystem not found - The requested subsystem was not found in the FM/IMS installation options module.

The specified subsystem has not been included in the FM/IMS installation options module.

If you want FM/IMS functions to have access to this subsystem, ask the FM/IMS administrator to add the subsystem to the FM/IMS installation options module.

FMNIA046

Subsystem not active - The requested subsystem is not currently active.

The specified subsystem is not active, so you cannot access it in BMP mode.

Contact the system administrator to determine why the subsystem is not active or, if you are permitted to do so, access the subsystem in DLI mode.

FMNIA047

Invalid value for parameter AGN. Patterns are not permitted.

The AGN parameter specifies a pattern. This parameter does not support patterns.

If REGNTYPE is set to BMP, and the subsystem specified in the IMSID parameter uses AGNs, specify an AGN that you have authority to use and that will provide the batch function with the access that it requires. Otherwise, remove the AGN parameter from the FMNIMSIN input.

FMNIA048

Invalid value for parameter IMSID. Patterns are not permitted.

The IMSID parameter specifies a pattern. This parameter does not support patterns.

Specify the ID of the IMS subsystem that the database you want to access is defined in.

FMNIA049

IMS subsystem &SSID is not active.

The subsystem specified in the IMSID parameter (&SSID) is not active, so you cannot access it in BMP mode.

Contact the system administrator to determine why the subsystem is not active or, if you are permitted to do so, access the subsystem in DLI mode.

FMNIA051

AGN required - The IMS subsystem uses AGNs and AGNs for the subsystem are not listed in the FM/IMS installation options module. So you must enter an AGN name.

AGN selection is only available when AGNs for the subsystem are listed in the FM/IMS installation options module.

Specify an AGN that you have authority to use, and that will provide the function with the access that it requires.

FMNIA052

No subsystem selected - No subsystem was selected on the Subsystem Selection panel.

IMS Subsystem Name is a required field, and you did not select a subsystem.

If you want to move forward in the dialog, you must either select a subsystem on the Subsystem Selection panel, or specify a subsystem in the IMS Subsystem Name field.

FMNIA053

Status refreshed - The status of the listed IMS subsystems has been refreshed.

FM/IMS has rechecked the status of the listed IMS subsystems, and refreshed the status fields on the screen.

No action is required.

FMNIA054

AGNs not used - The subsystem does not use AGNs. Leave field blank.

You have specified an AGN, and the subsystem does not use AGNs.

Blank out the AGN field (online functions), or remove the AGN parameter from the FMNIMSIN input (batch functions).

FMNIA055

AGN pattern not allowed - AGNs for the subsystem are not listed in the FM/IMS installation options module. So you must enter the full AGN name.

Self explanatory.

Specify an AGN that you have authority to use, and that will provide the function with the access that it requires.

FMNIA056

View not replaced - The view was not saved and the existing data was not replaced.

Because you pressed the EXIT or CANCEL key on the View Replace pop-up panel, the view was not saved, and the existing data was not replaced.

No action is required.

FMNIA057

DBD &DBNAME not found - Logically related DBD &DBNAME not found in the DBD libraries for subsystem (&SSID)

FM/IMS requires the following DBDs to be in at least one of the DBD libraries for the specified subsystem &SSID:
  • The DBD for the database you specified.
  • The DBD for each database that is logically related to the database you specified.
Database &DBNAME is logically related to the database you specified, but its DBD was not found in the DBD libraries for subsystem &SSID.

The DBD libraries for subsystem &SSID are specified on the PSB and DBD Data Sets panel (option 0.6.7). Either include a DBD for database &DBNAME in one of the DBD libraries listed on that panel, or update this list to include a DBD library that has a DBD for database &DBNAME. You will only be able to update the list when the DBD libraries for the subsystem are not fixed. When the DBD libraries for the subsystem are fixed, the DBD data set names panel fields are protected, and only the FM/IMS administrator can update the list.

FMNIA058

IMS MACLIB &DSN dynamic allocation error - DYNALLOC reason code is X'&RSN'.

An attempt to allocate IMS MACLIB &DSN failed. X'&RSN' is the error reason code that the DYNALLOC macro returned.

For an explanation of the DYNALLOC error reason code, see the z/OS MVS Programming: Authorized Assembler Services Guide. Use this information to determine why the data set could not be allocated.

FMNIA061

Data set in use - Allocation of data set failed because data set is in use by another user or job.

An attempt to allocate this database data set failed. The dynamic allocation request failed because the data set is allocated to another user, or job, and its usage attribute conflicts with your request.

To obtain a list of the jobs and users allocated to the data set, attempt to edit the data set (use ISPF option 2 "Edit", or ISPF option 3.4 "Data Set List Utility"), and when ISPF issues the message 'Data set in use', enter the HELP command (F1) twice, and ISPF will display the required information on the Data Set Contention panel.

FMNIA062

Load of DBD &DBNAME failed with abend code &CC and reason code &RSN.

An attempt to load DBD &DBNAME failed. &CC is the abend code for the abend that would have been issued had there not been error recovery. &RSN is the reason code associated with the abend code.

For an explanation of the abend and associated reason code, see z/OS MVS System Codes. Use this information to determine why the DBD could not be loaded.

FMNIA063

Load of PSB &PSBNAME failed with abend code &CC and reason code &RSN.

An attempt to load PSB &PSBNAME failed. &CC is the abend code for the abend that would have been issued had there not been error recovery. &RSN is the reason code associated with the abend code.

For an explanation of the abend and associated reason code, see z/OS MVS System Codes. Use this information to determine why the PSB could not be loaded.

FMNIA064

Database mismatch - Found member &DBNAME1 in Template library &DSN. Expected it to be a template for database &DBNAME1, but it was a template for database &DBNAME2. You cannot use this template to browse/edit/extract/ or print database &DBNAME1.

Because you have selected 'New' for View, or Criteria usage, the function attempts to create a view, or criteria set, from a template for the specified database (&DBNAME1). FM/IMS searches user, or administrator, specified template libraries for the template. Which template libraries FM/IMS searches depends on which subsystem you select. The template libraries that FM/IMS searches are listed on the Template Data Sets panel (option 0.6.8). FM/IMS searches these libraries in the order in which they are specified, and uses the first member it finds with the specified database name (&DBNAME1).

FM/IMS found a member with the specified database name (&DBNAME1), but cannot use it because it is not a template for database &DBNAME1.

Do one of the following:
  • Delete member &DBNAME1 from the Template library &DSN, and then, using option 4.1, create a template for database &DBNAME1 and save it in the Template library &DSN.
  • Update the list of Template libraries on the Template Data Sets panel to only include Template libraries with valid templates. You will only be able to update the list when the Template libraries for the subsystem are not fixed. When the Template libraries for the subsystem are fixed, the Template data set name panel fields are protected, and only the FM/IMS administrator can update the list.

FMNIA066

Create/Edit failed - Create/Edit failed because DBD &DBNAME was not found in the DBD libraries specified in the template/view/criteria set.

One of the following failures occurred:

  1. The CT command (Create view/criteria set from template) failed because the DBD for database &DBNAME (that is, the database the template is for) was not found in the DBD libraries specified in the template.
  2. The CM command (Create view/criteria set from model) failed because the DBD for database &DBNAME (that is, the database the model view/criteria set is for) was not found in the DBD libraries specified in the model view/criteria set.
  3. The Edit view/criteria set failed because the DBD for database &DBNAME (that is, the database the view/criteria set is for) was not found in the DBD libraries specified in the view/criteria set.

A different response is required for failure 1 than for failure 2 and 3.

For failure 1, first you need to determine which DBD libraries are specified in the template. To determine this, use option 4.1. If you specify the Template data set name and member on the Template Entry panel and press Enter, the DBD Library List panel is displayed. The panel displays a list of the DBD libraries specified in the template.

There are two ways you can proceed from here. Either:

  1. Include a DBD for database &DBNAME in one of the DBD libraries listed on that panel, or
  2. Update this list to include a DBD library that has a DBD for database &DBNAME.

To save the template, press Enter, followed by the Exit key.

Either of these actions will resolve this problem. The remainder of the text describes the response for failure 2 and 3.

For failure 2, the view/criteria set refers to the model view/criteria set.

For failure 3, the view/criteria set refers to the view/criteria set you attempted to edit:

  • Update the view/criteria set from the template it is based on. To update the view, use the U command on the View Entry panel (option 4.2). To update the criteria set, use the U command on the Criteria Set Entry panel (option 4.3). If the view/criteria set was based on the latest version of the template, FM/IMS issues message FMNIA083 'Update not required - View/Criteria set did not require any updates from the template it was created from. The template is in data set member &DSN. Otherwise, FM/IMS updates the view/criteria set and issues message FMNIA082/FMNIA131 'View /Criteria set updated - View/Criteria set has received updates from the template it was created from. The template is in data set member &DSN. Take note of the template data set name and member (&DSN) specified in these messages.
  • If the update was required, the update may have resolved the problem. Issue the CM or E command again to see if it has.
  • If the problem still exists, you need to determine which DBD libraries are specified in the template that the view/criteria set is based on. That is, the template in &DSN. To determine this, use Option 4.1. If you specify the template data set name and member on the Template Entry panel and press Enter, the DBD Library List panel is displayed. This panel displays a list of the DBD libraries specified in the template.

There are two ways you can proceed from here. Either include a DBD for database &DBNAME in one of the DBD libraries listed on that panel, or do the following:

  • Update this list to include a DBD library that has a DBD for database &DBNAME.
  • To save the template, press Enter, followed by the Exit key. Then update the view/criteria set from the template as you did before.

Either of these actions will resolve this problem.

FMNIA067

Create/Edit failed - Create/Edit failed because member &DBNAME of DBDLIB &DSN does not contain a valid DBD for database &DBNAME.

One of the following failures occurred:

  1. The CT command (Create view/criteria set from template) failed.
  2. The CM command (Create view/criteria set from model) failed.
  3. The E command (Edit view/criteria set) failed.
  • For failure 1, &DBNAME is the name of the database the template is for and &DSN is a DBD library specified in the template. FM/IMS searches the DBD libraries specified in the template for member &DBNAME. This member is found in the DBD library &DSN, but it does not contain a valid DBD for database &DBNAME, so the command fails.
  • For failure 2, &DBNAME is the name of the database the model view/criteria set is for and &DSN is a DBD library specified in the model view/criteria set. FM/IMS searches the DBD libraries specified in the model view/criteria set for member &DBNAME. This member is found in the DBD library &DSN, but it does not contain a valid DBD for database &DBNAME, so the command fails.
  • For failure 3, &DBNAME is the name of the database the view/criteria set is for and &DSN is a DBD library specified in the view/criteria set. FM/IMS searches the DBD libraries specified in the view/criteria set for member &DBNAME. This member is found in the DBD library &DSN, but it does not contain a valid DBD for database &DBNAME, so the command fails.

Either replace the member with a valid DBD for database &DBNAME, or do the following:

  • For failure 1, use options 4.1, or 4.4, to correct the DBD library list specified in the template.

The remainder of the text describes the response for failure 2 and 3. For failure 2, the view or criteria set refers to the model view or criteria set. For failure 3, the view or criteria set refers to the view or criteria set you attempted to edit:

  • Update the view or criteria set from the template it is based on. To update the view, use the U command on the View Entry panel (option 4.2). To update the criteria set, use the U command on the Criteria Set Entry panel (option 4.3). If the view or criteria set was based on the latest version of the template, FM/IMS issues message "FMNIA083" (FMNIA083). Otherwise, FM/IMS updates the view or criteria set and issues message "FMNIA082" (FMNIA082) or message "FMNIA131" (FMNIA131). Take note of the template data set name, and member (&DSN), specified in these messages.
  • If the update was required, the update may have resolved the problem. Issue the CM, or E, command again to see if it has.
  • If the problem still exists, specify the template data set name, and member (&DSN), on the Template Entry panel (option 4.1), and press Enter; the DBD Library List panel is displayed. This panel displays a list of the DBD libraries specified in the template.
    • Update this list to only include DBD libraries with valid DBDs.
    • To save the template, press Enter, followed by the Exit key. Then update the view or criteria set from the template as you did before.

These actions will resolve this problem.

FMNIA068

&PARM data set &DSN is not partitioned.

The data set &DSN specified in parameter &PARM is not partitioned. You must specify a PDS(E) in this parameter.

Specify a PDS(E).

FMNIA069

The ACBGEN that builds the blocks for the dynamic PSB failed with return code &RC.

The ACBGEN for the dynamic PSB your batch function was generating failed with a return code of &RC.

The job SYSPRINT output will include the ACBGEN listing. Use the ACBGEN listing to determine the cause of the problem.

FMNIA070

No dynamic PSB available - All the dynamic PSB names available to this BMP are currently in use.

There are a finite number of dynamic PSB names available for use by concurrent FM/IMS functions run in BMP mode. Currently, they are all being used.

Try again later. If you get this message frequently, notify the FM/IMS administrator.

FMNIA071

ATTACH of IMS control region program failed with return code &RC.

An attempt to attach the IMS region controller failed with a return code of &RC.

For an explanation of the ATTACH macro return codes, see z/OS MVS Programming: Authorized Assembler Services Guide. Check the z/OS system log for error messages issued during the processing of the ATTACH macro.

FMNIA072

Segment not found - No &SEGNAME segment occurrence with the specified key values was found.

FM/IMS issued a GU call for a &SEGNAME segment occurrence, but the call received a GE status code. IMS returns this status code when it cannot find a segment that satisfies the segment search arguments (SSAs) specified in the call.

No action is required.

FMNIA073

Call to DL/I failed with status code &SC.

A DL/I database retrieval call received a status code of &SC.

For an explanation of the status code, see IMS Messages and Codes Vol 4. Use this information to determine why the retrieval call received a bad status code.

FMNIA075

RECON1/RECON2/RECON3 data set &DSN dynamic allocation error; DYNALLOC reason code=X'&RSN'.

An attempt to allocate RECON data set &DSN failed. X'&RSN' is the error reason code that the DYNALLOC macro returned.

For an explanation of the DYNALLOC error reason code, see z/OS MVS Programming: Authorized Assembler Services Guide. Use this information to determine why the data set could not be allocated.

FMNIA077

Edit of an HSAM database is not supported.

The specified database is an HSAM database. FM/IMS does not support the edit of HSAM databases because IMS does not support the Delete (DLET) and Replace (REPL) calls. And Insert (ISRT) calls are only allowed when the database is being loaded.

If you want to update this database, it must be reloaded.

FMNIA078

Edit of an SHSAM database is not supported.

The specified database is an SHSAM database. FM/IMS does not support the edit of SHSAM databases because IMS does not support the Delete (DLET) and Replace (REPL) calls. And Insert (ISRT) calls are only allowed when the database is being loaded.

If you want to update this database, it must be reloaded.

FMNIA081

Invalid value - Specify one of the following relational operators: EQ GT GE LE NE UQ = > < >= <= ¬=

The message is issued on the Key Specification panel when an invalid value is entered in one of the RO (Relational Operator) fields. The values specified in these fields are used when building the SSAs for the GU call that the panel issues.

When you want an unqualified SSA at this level, specify UQ in the field. Otherwise, specify the relational operator you want the SSA to use.

FMNIA082

View updated - View has received updates from the template it was created from. The template is in data set member &DSN.

The template that the view was created from had been modified since the view was last updated, so the view has been updated as you requested. The template that the view was created from is in data set member &DSN.

No action is required.

FMNIA083

Update not required - View/Criteria set did not require any updates from the template it was created from. The template is in data set member &DSN.

You requested an update of the view/criteria set, but the update was not performed because it was not required. The update is only performed when the template that the view/criteria set was created from has been modified. The template that the view was created from is in data set member &DSN.

No action is required.

FMNIA084

Criteria not replaced - The criteria set was not saved and the existing data was not replaced.

You pressed the EXIT or CANCEL key on the Criteria Replace pop-up panel, so the criteria set was not saved, and the existing data was not replaced.

No action is required.

FMNIA085

&PARM data set &DSN is not a load library.

The data set &DSN specified in parameter &PARM is not a load library. You must specify a load library in this parameter.

Specify a load library.

FMNIA086

&PARM data set &DSN was not found in the catalog.

The data set &DSN specified in parameter &PARM was not found in the catalog. You must specify a cataloged data set.

Specify a cataloged data set.

FMNIA087

DBDMEM member &MBR was not found in the specified DBD libraries.

The member &MBR specified in parameter DBDMEM was not found in the DBD libraries specified in the DBDDSN, DBDDSN2, DBDDSN3, DBDDSN4, DBDDSN5, and DBDDSN6 parameters.

Specify a DBD library that has the required DBD member.

FMNIA093

Criteria set created - Criteria set created and saved in the specified criteria data set.

Self explanatory.

No action is required.

FMNIA094

Only 255 criteria subsets are allowed

An attempt to create a new field criteria subset, or repeat an existing field criteria subset, failed because the criteria set would exceed the maximum allowable number of field criteria subsets. 255 is the maximum number of field criteria subsets that a criteria set is allowed to have.

None.

FMNIA095

Criteria set saved - Criteria set has been saved in the criteria data set.

Self explanatory.

No action is required.

FMNIA100

Load of a logical database is not supported.

The specified database is a logical database. FM/IMS does not support the load of logical databases.

Load the data into the physical databases.

FMNIA101

Load of an index database is not supported.

The specified database is an index database. IMS does not support the load of an index as a separate database.

Load the data into the indexed databases; IMS takes care of the indexes.

FMNIA102

Invalid for Fast Path - Fast Path databases can only be processed in a BMP region.

The specified database is a Fast Path database. Fast Path databases cannot be processed in DL/I batch regions.

Select BMP for the Region type.

FMNIA103

No segment layout selected

The Segment Layout Selection panel was displayed because the segment that you selected has multiple segment layouts. You did not select a segment layout on that panel.

If you want to insert the segment that you selected, you must select the segment layout that you want the insert to use.

FMNIA104

Load of an MSDB database is not supported.

The specified database is an MSDB database. FM/IMS does not support the load of MSDB databases.

Use the MSDB Maintenance utility (DBFDBMA0) to create a z/OS sequential data set for an initial load of the MSDB database. For information on how to do this see IMS Utilities Reference: Database and Transaction Manager.

FMNIA105

The Load file does not contain a valid header record.

Self explanatory.

Check that you have included a header record in the Load file. If you have, check that the data in this record is correctly formatted. For information on the layout of the header record, see Extract data layout. Alternatively, you can get the Extract dialog, or Extract job, to create a template for the Load file. The template provides you with the correct layout for the header record. Using this template when you edit the header record will reduce the effort required to format the data.

FMNIA109

DSPURX00 call failed to obtain the ddnames and data set names for DB &DBNAME. The DBRC command received return code &RC.

The batch function you ran calls the Database Recovery Control Utility (DSPURX00) to obtain the ddnames and data set names for:
  • The HALDB database you specified; and
  • All HALDB databases that are logically related to the HALDB database you specified
The call that was attempting to obtain the ddnames, and data set names for database &DBNAME, failed with a return code of &RC.

Add the following DD statement to the JCL and rerun the job:

//FMN1DPRT DD SYSOUT=*

The job output will include the DBRC listing. Use the listing to determine the cause of the problem.

FMNIA111

Press ENTER to confirm usage of the specified data set(s).

Self explanatory.

Check the displayed database data set names. If they are the data sets that you want the function to use, press Enter.

FMNIA112

Recall failed - Data set is migrated or archived and the recall of the data set failed.

The data set that you specified is migrated or archived. FM/IMS attempted to recall this data set, but the recall failed.

See the DFHSM (or equivalent product) messages issued prior to this message for detailed information on the cause of the failure.

FMNIA114

Edit/Browse active - FM/IMS supports only one Edit/Browse dialog per user.

You have selected the Edit or Browse dialog, but you are already running an Edit or Browse dialog on another logical screen. FM/IMS supports only one Edit/Browse dialog per user.

Exit the active Edit/Browse dialog and then try again. If you receive this message when you have no active Edit/Browse dialogs on any of your logical screens, log off and then log back on.

FMNIA115

Extract dialog active - FM/IMS supports only one Extract dialog per user.

You have selected the Extract dialog, but you are already running an Extract dialog on another logical screen. FM/IMS supports only one Extract dialog per user.

Exit the active Extract dialog and then try again. If you receive this message when you have no active Extract dialogs on any of your logical screens, log off and then log back on.

FMNIA116

Load dialog active - FM/IMS supports only one Load dialog per user.

You have selected the Load dialog, but you are already running a Load dialog on another logical screen. FM/IMS supports only one Load dialog per user.

Exit the active Load dialog and then try again. If you receive this message when you have no active Load dialogs on any of your logical screens, log off and then log back on.

FMNIA117

Template dialog active - FM/IMS supports only one Template dialog per user.

You have selected the Template dialog, but you are already running a Template dialog on another logical screen. FM/IMS supports only one Template dialog per user.

Exit the active Template dialog and then try again. If you receive this message when you have no active Template dialogs on any of your logical screens, log off and then log back on.

FMNIA118

View dialog active - FM/IMS supports only one View dialog per user.

You have selected the View dialog, but you are already running a View dialog on another logical screen. FM/IMS supports only one View dialog per user.

Exit the active View dialog and then try again. If you receive this message when you have no active View dialogs on any of your logical screens, log off and then log back on.

FMNIA119

Criteria dialog active - FM/IMS supports only one Criteria dialog per user.

You have selected the Criteria Set dialog, but you are already running a Criteria Set dialog on another logical screen. FM/IMS supports only one Criteria Set dialog per user.

Exit the active Criteria Set dialog and then try again. If you receive this message when you have no active Criteria Set dialogs on any of your logical screens, log off and then log back on.

FMNIA121

XKEY data set &DSN created.

You issued the XKEY command on an IMS data panel. This is a request to create a data set that contains the keys of all the root segments between the current position and the end of the database, or the keys of every nth root segment between the current position and the end of the database. This message is issued when the XKEY data is successfully created.

No action is required.

FMNIA122

Edit of a logical database with KEY-only segments is not supported.

You specified a logical database. Its DBD specifies KEY sensitivity for both the logical child and destination parent of a concatenated segment or KEY sensitivity for a nonconcatenated segment. FM/IMS does not support the Edit of logical databases with such segments.

No action is required.

FMNIA123

REPEAT/INSERT not allowed - REPEAT/INSERT of a concatenated segment is only supported when DATA sensitivity has been specified for both the logical child and the destination parent.

You have requested the insertion of a concatenated segment into the logical database. However, FM/IMS did not attempt to insert the segment, because the DBD does not specify DATA sensitivity for both the logical child and the destination parent of the concatenated segment. IMS only supports the insertion of a concatenated segment when the DBD specifies DATA sensitivity for both parts of the concatenated segment.

No action is required.

FMNIA124

No logical relationships - No relationship criteria exist because the database has no logical relationships.

You issued the E line command against the relationship criteria subset. This is a request to edit the relationship criteria. However, the request cannot be honored because there are no relationship criteria. Only databases with logical relationships have relationship criteria, and this database has no logical relationships.

No action is required.

FMNIA125

IMS log data set deleted - The IMS log data set &DSN has been deleted.

The IMS log data set that the Edit session used (&DSN) has been deleted. The data set is deleted when the Edit session ends normally, and you select Delete for the IMS log option on the Edit Entry panel.

No action is required.

FMNIA126

IMS log data set kept - The IMS log data set &DSN has been kept.

The IMS log data set that the Edit session used (&DSN) has been kept. The data set is kept when you select Keep for the IMS log option on the Edit Entry panel. It is also kept when the Edit session does not end normally.

No action is required.

FMNIA127

Chkpt &ID taken - A checkpoint with ID &ID was written to the IMS log.

This message is issued when you issue the SAVE command on the Database Positioning panel. It is also issued when the Database Positioning panel is first displayed if, as is normally the case, FM/IMS takes a checkpoint at the start of the Edit session. With one exception, checkpoint messages are not issued on the IMS data panel. The checkpoint ID in the CHKPT field is incremented when a checkpoint is taken, so they are not required on that panel. The exception occurs when checkpoints are taken during a Change All, or Repeat All, operation.

No action is required.

FMNIA128

Delete unsuccessful - The Delete was unsuccessful because the GET HOLD call failed to retrieve the segment.

You issued the D line command, but the attempt to delete the segment on that line was unsuccessful because the GET HOLD call failed. Depending on the status code that the GET HOLD call receives, FM/IMS either displays a pop-up panel, or issues a message before it issues this message.
  • If the GET HOLD call receives the GE status code, then the Segment Update/Delete Warning pop-up panel is displayed.
  • If the GET HOLD call receives the FH or BA status code, then the Unavailable Segment Warning pop-up panel is displayed.
  • Otherwise, a message is issued that tells you the status code that the GET HOLD call received.

See the previous message pop-up panel for information on the cause of this failure.

FMNIA129

No segments selected - View must have at least one segment selected

You attempted to save or use a view that has all its segments deselected. A view that has all its segments deselected would not return any segments, so FM/IMS does not allow you to do this.

Select at least one segment.

FMNIA130

Invalid command syntax - The DEPENDENT, SEGMENT and REC parameters are not supported in ZOOM mode.

You issued a FIND, or CHANGE, command with the DEPENDENT, SEGMENT, or REC parameter when in ZOOM mode. The DEPENDENT, SEGMENT, and REC parameters are not supported in ZOOM mode.

Get out of ZOOM mode, then issue the command again. To get out of ZOOM mode, press the EXIT key or the CANCEL key, or issue the ZOOM command.

FMNIA131

Criteria set updated - Criteria set received updates from the template it was created from. The template is in data set member &DSN.

The template that the criteria set was created from had been modified since the criteria set was last updated, so the criteria set was updated as you requested. The template that the criteria set was created from is in data set member &DSN.

No action is required.

FMNIA132

Checkpoint &ID taken. Uncommitted changes made during this Edit sessiona have been saved.

Some database changes that you made during this Edit session had not been committed when you used the EXIT key to leave the Database Positioning panel. Because you pressed the EXIT key, the uncommitted changes were saved.

No action is required.

FMNIA133

DBD member not found - The DBD for database &DBNAME not found in the DBD libraries for subsystem &SSID.

FM/IMS requires the DBD for the specified database (&DBNAME), but it was not found in the DBD libraries for the specified subsystem (&SSID).

The DBD libraries for subsystem &SSID are specified on the PSB and DBD Data Sets panel (option 0.6.7). Either include a DBD for database &DBNAME in one of the DBD libraries listed on that panel, or update this list to include a DBD library that has a DBD for database &DBNAME. You will only be able to update the list when the DBD libraries for the subsystem are not fixed. When the DBD libraries for the subsystem are fixed, the DBD data set names panel fields are protected, and only the FM/IMS administrator can update this list.

FMNIA134

No segments selected - Criteria subset must have at least one segment selected.

You attempted to exit the criteria subset with all its segments deselected. A subset with all its segments deselected would not return any segments, so FM/IMS does not allow you to to this.

Pressing the CANCEL key will allow you to exit, but the changes you have made to the subset will not be saved. If you want your changes to be saved when you exit, select at least one segment, then press the EXIT key.

FMNIA135

No layouts selected - Criteria subset must have at least one segment layout selected.

You attempted to exit the criteria subset with all its segment layouts deselected. A subset with all its segment layouts deselected would not return any segments, so FM/IMS does not allow you to do this.

Pressing the CANCEL key will allow you to exit, but the changes you have made to the subset will not be saved. If you want your changes to be saved when you exit, select at least one segment layout, then press the EXIT key.

FMNIA136

The PCB you are using does not allow segment insertion.

You have issued the INSERT primary command, but the PCB that you are using does not allow segment insertion.

Use a PCB that allows segment insertion.

FMNIA137

Missing segments - Database &DBNAME has segments that are not defined in the template.

The DBD that this template is based on has segments that are not defined in this template. Updating the template will rectify this. FM/IMS will not allow you to use this template to create views, or criteria sets, until you have updated it.

Using option 4.1, or option 4.4, update the template.

FMNIA138

Missing segments - Database &DBNAME has segments that are not defined in the view/criteria set. Update the view/criteria set and, if this fails to remedy the problem, update the template &DSN that the view/criteria set was created from then update the view/criteria set again.

&DBNAME is the name of the database that the view or criteria set is for. The DBD for this database has segment types that are not defined in the view or criteria set.

Use View update (option 4.5) to update the view, using the IMS template that the view was created from. If after successful completion the IMS segments are still missing, you will need to update the IMS template &DSN to include the new IMS segments using Templates (option 4.1). Repeat the process of updating the view using View update (option 4.5).

FMNIA139

Warning: The view/criteria set was not based on the latest version of the template it was created from.

A batch function issues this warning message when it determines that the view/criteria set is not based on the latest version of the template it was created from. The batch function ignores this error and continues processing.

Check the output from the job. Update the view/criteria set. To update a view use either option 4.2, or option 4.5. To update a criteria set, use option 4.3, or option 4.6.

FMNIA149

CANCEL not active - The CANCEL command is not active because no IMS log data set was allocated at the start of the Edit session.

Some database changes that you made during this Edit session have not been committed. You issued the CANCEL command on the Database Positioning panel, which indicates that you want these changes backed out. However, IMS cannot back out these changes, because an IMS log was not allocated at the start of the Edit session.

If you want the option of discarding your uncommitted changes when editing in DLI mode, you must select Keep, or Delete, for the IMS log option on the Edit Entry panel.

FMNIA150

CANCEL not active - The CANCEL command is not active because your Edit session did not request dynamic backout.

Some database changes that you made during this Edit session have not been committed. You issued the CANCEL command on the Database Positioning panel, which indicates that you want these changes backed out. However, IMS cannot back out these changes, because your Edit session did not request dynamic backout.

If you want the option of discarding your uncommitted changes when editing in DLI mode, you must select the Dynamic backout option on the DLI Mode Parameters panel. What you are specifying on this panel is the subsystem setting for the Dynamic backout option, so ensure that it is selected for each subsystem that you require it for.

FMNIA152

RESLIB &DSN not found. Correct the RESLIBx parameter for subsystem &SSID in FMN1POPT.

The function attempted to use the default RESLIB data sets for subsystem &SSID. However, one of these data sets (&DSN) could not be found. The default RESLIB data sets are specified in the FM/IMS installation options module.

Ask the FM/IMS administrator to correct the RESLIB parameter on the FMN1POPI macro statement for subsystem &SSID, and then reassemble and link-edit the FM/IMS installation options module.

FMNIA153

RESLIB &DSN not a loadlib. Correct the RESLIBx parameter for subsystem &SSID in FMN1POPT.

The function attempted to use the default RESLIB data sets for subsystem &SSID. However, one of these data sets (&DSN) is not a load library. The default RESLIB data sets are specified in the FM/IMS installation options module.

Ask the FM/IMS administrator to correct the RESLIB parameter on the FMN1POPI macro statement for subsystem &SSID, and then reassemble and link-edit the FM/IMS installation options module.

FMNIA154

RESLIB &DSN for &SSID not found. Correct the data set name on the DLI Mode Data Sets 1 panel.

The function attempted to use the RESLIB data sets for subsystem &SSID, specified on the DLI Mode Data Sets 1 panel. However, one of these data sets (&DSN) could not be found.

Correct the data set name on the DLI Mode Data Sets 1 panel (option 0.6.2).

FMNIA155

DOPT ACBLIB &DSN not found. Correct the DYNACB parameter for subsystem &SSID in FMN1POPT.

The function attempted to use the DOPT ACBLIB data set (&DSN) for subsystem &SSID. However, the data set could not be found. The DOPT ACBLIB data set is specified in the FM/IMS installation options module.

Ask the FM/IMS administrator to correct the DYNACB parameter on the FMN1POPI macro statement for subsystem &SSID, and then reassemble and link-edit the FM/IMS installation options module.

FMNIA156

CANCEL not active - The CANCEL command is not active because the PSB that your Edit is using has no IO PCB.

Some database changes that you made during this Edit session have not been committed. You issued the CANCEL command on the Database Positioning panel, which indicates that you want these changes backed out. However, IMS cannot back out these changes because the PSB that your Edit is using has no IO PCB.

If you want the option of discarding your uncommitted changes when editing in DLI mode, you must use a PSB that has an IO PCB.

FMNIA158

No PCB selected - A PCB is required and no PCB has been selected.

You left the PCB Selection panel without selecting a PCB.

If you want to use the PSB that you specified, you must either select one of the PCBs displayed on the PCB Selection panel, or specify in the Database name field, the name of a database that the PSB can give you access to.

FMNIA159

DBD &DBNAME not found - This PSB has a PCB for the database &DBNAME and its DBD was not found in the DBD libraries for subsystem &SSID.

FM/IMS requires the DBD for each database specified in the PSB to be in the DBD libraries for the specified subsystem (&SSID). The PSB has a PCB for database &DBNAME, but the DBD for database &DBNAME was not found in the DBD libraries for subsystem &SSID.

The DBD libraries for subsystem &SSID are specified on the PSB and DBD Data Sets panel (option 0.6.7). Either include a DBD for database &DBNAME in one of the DBD libraries listed on that panel, or update this list to include a DBD library that has a DBD for database &DBNAME. You will only be able to update the list when the DBD libraries for the subsystem are not fixed. When the DBD libraries for the subsystem are fixed, the DBD data set names panel fields are protected, and only the FM/IMS administrator can update the list.

FMNIA162

Not a DLI region PSB - PSB cannot be used in DLI mode because it has a PCB for a Fast Path database.

You have selected DLI for the Region type. However, the PSB that you specified cannot be used when the function is run in a DL/I batch processing region because it has a PCB for a Fast Path database.

Select BMP for the Region type or use another PSB.

FMNIA163

PSB &PSBNAME has only one DB PCB and the PCB is read-only; the function cannot be performed with a read-only PCB.

The PSB that you have specified (&PSBNAME) has only one DB PCB. The function you are using cannot use this PCB because it requires update access to databases, and the PCB only provides read access.

Use a PSB with a PCB that provides update access to the database that you want the function to process.

FMNIA170

PCB for database &DBNAME has PROCOPT=&OPT; the function cannot be performed with a read-only PCB.

The PSB that you have specified has only one PCB for the database that you specified (&DBNAME). The function you are using cannot use this PCB because it requires update access to this database, and the PCB only provides read access.

Use a PSB with a PCB that provides update access to the database.

FMNIA171

SAVE not active - the SAVE command is not active because the PSB that your Edit is using has no IO PCB.

You issued the SAVE command. This is a request to save all your uncommitted database changes. To do this FM/IMS issues a checkpoint call. However, a checkpoint cannot be taken because the PSB your Edit is using has no IO PCB.

Your changes are saved when you return to the Edit Entry panel. This is the only way you can save your changes when the PSB has no IO PCB. If you want to use the SAVE command when editing in DLI mode, you must use a PSB that has an IO PCB.

FMNIA172

&CMD not active - &CMD command is not active when in ZOOM mode.

You are in ZOOM mode and the command you issued (&CMD) is not supported in ZOOM mode.

Get out of ZOOM mode, then issue the command again. To get out of ZOOM mode, press the EXIT key, or CANCEL key, or issue the ZOOM command.

FMNIA173

Segment not a parent - The segment name specified in the PARENT command must be the name of a parent of the current segment type.

You issued the PARENT command. The PARENT command changes your position from the current segment occurrence, to a parent of the current segment occurrence. However, the segment name you specified in the PARENT command is not the name of a parent of the current segment type.

Specify the name of a parent of the current segment type.

FMNIA174

Child not found - The requested child segment occurrence was not found.

You issued the CHILD command. The CHILD command allows you to change your position from the current segment occurrence to any of its dependent segment occurrences. However, FM/IMS could not find the child segment occurrence that you requested.

No action is required.

FMNIA176

Segment not found - No segment was found that has keys greater than or equal to the specified key values.

FM/IMS issued a GU call for the segment you selected on the Database Positioning panel, but the call received a GE status code. IMS returns this status code when it cannot find a segment that satisfies the segment search arguments (SSAs) specified in this call. The following describes the SSAs used in the call:

  • There was an SSA for the selected segment, and an SSA for each of its parents.
  • If the Key Value field for a segment in the path so defined contained spaces or low values, then an unqualified SSA was used at that level.
  • If the Key Value field for the root segment did not contain spaces, or low values, and you are accessing the database via a secondary index, then the SSA at the root level has a qualification statement that specifies the secondary index key field, a greater-than-or-equal-to relational operator, and the specified key value.
  • Otherwise, the SSA has a qualification statement that specifies the key field of the segment, a greater-than-or-equal-to relational operator, and the specified key value.

These SSAs are used when you press the GE (Greater than or Equal to) key, and the root segments of the database are in key, or a secondary processing, sequence.

No action is required.

FMNIA177

Segment not found - No segment was found that has a root key equal to the specified root key value and dependent segment keys greater than or equal to the specified dependent segment key values.

FM/IMS issued a GU call for the dependent segment you selected on the Database Positioning panel, but the call received a GE status code. IMS returns this status code when it cannot find a segment that satisfies the segment search arguments (SSAs) specified in this call. The following describes the SSAs used in the call:

  • There was an SSA for the selected segment, and an SSA for each of its parents.
  • If the Key Value field for a segment in the path so defined contained spaces, or low values, then an unqualified SSA was used at that level.
  • If the Key Value field for the root segment did not contain spaces, or low values, then the SSA at the root level has a qualification statement that specifies the root key field, an equal-to relational operator, and the specified key value.
  • If the Key Value field for a dependent segment did not contain spaces, or low values, then the SSA for the dependent segment has a qualification statement that specifies the key field of the segment, a greater-than-or-equal-to relational operator, and the specified key value.

These SSAs are used in the call when you press the GE (Greater than or Equal to) key, and the root segments of the database are not in key, or a secondary processing, sequence.

No action is required.

FMNIA178

Segment not found - No segment was found with the specified key values.

FM/IMS issued a GU call for the segment you selected on the Database Positioning panel, but the call received a GE status code. IMS returns this status code when it cannot find a segment that satisfies the segment search arguments (SSAs) specified in this call. The following describes the SSAs used in the call:

  • There was an SSA for the selected segment, and an SSA for each of its parents.
  • If the Key Value field for a segment in the path so defined contained spaces, or low values, then an unqualified SSA was used at that level.
  • If the Key Value field for the root segment did not contain spaces, or low values, and you are accessing the database via a secondary index, then the SSA at the root level has a qualification statement that specifies the secondary index key field, an equal-to relational operator, and the specified key value.
  • Otherwise, the SSA has a qualification statement that specifies the key field of the segment, an equal-to relational operator, and the specified key value.

These SSAs are used in the call when you press the Enter key on the Database Positioning panel.

No action is required.

FMNIA179

Segment not found - No root segment was found with the specified key value. FM/IMS did not search for a root segment with a key greater than or equal to the specified key value because the root segments are not in key sequence.

FM/IMS issued a GU call for the root segment you selected on the Database Positioning panel, but the call received a GE status code. IMS returns this status code when it cannot find a segment that satisfies the segment search arguments (SSAs) specified in this call. The following describes the SSAs used in the call:

  • If the Key Value field for the root segment contained spaces, or low values, then an unqualified SSA was used at the root level.
  • Otherwise, the SSA, at the root level, has a qualification statement that specifies the root key field of the segment, an equal-to relational operator, and the specified key value.

This message is only issued when you select a root segment, you press the GE (Greater than or Equal to) key, and the root segments of the database are not in key, or a secondary processing, sequence.

No action is required.

FMNIA181

EDIT not active - The Edit line command is only active when the Edit or Browse is using a view.

You issued the E (Edit) line command on the Database Positioning panel. This is a request to edit a segment in the view that your Edit or Browse is using. However, your request cannot be honored because the Edit or Browse is not using a view.

If you want the Edit/Browse to use a view, return to the Edit/Browse Entry panel and select New, or Existing, for the View usage.

FMNIA184

SELECT not active - The SELECT command is only active when the Edit or Browse is using a view.

You issued the SELECT primary, or line, command on the Database Positioning panel. This is a request to select or deselect segments in the view that your Edit or Browse is using. However, your request cannot be honored because the Edit or Browse is not using a view.

If you want the Edit/Browse to use a view, return to the Edit/Browse Entry panel and select New, or Existing, for the View usage.

FMNIA185

UNDO not active - The UNDO command is not active because no IMS log data set was allocated at the start of the Edit session.

You issued the UNDO command. This is a request to back out all the database changes you have made since the last checkpoint. However, IMS cannot back out your changes because no IMS log data set was allocated at the start of the Edit session.

If you want to use the UNDO command when editing in DLI mode, you must select Keep, or Delete, for the IMS log option on the Edit Entry panel.

FMNIA186

No updates - You issued the UNDO command but you have not made any database changes since the last checkpoint or rollback, so FM/IMS did not issue a rollback call.

You issued the UNDO command. This is a request to back out all the database changes you have made since the last checkpoint, or rollback. To do this, FM/IMS issues a rollback (ROLB) call. However, there have been no database changes since the last checkpoint, or rollback, so FM/IMS did not issue a ROLB call.

No action is required.

FMNIA187

UNDO not active - The UNDO command is not active because your Edit session did not request dynamic backout.

You issued the UNDO command. This is a request to back out all the database changes you have made since the last checkpoint. However, IMS cannot back out your changes because your Edit session did not request dynamic backout.

If you want to use the UNDO command when editing in DLI mode, you must select the Dynamic backout option on the DLI Mode Parameters panel. What you are specifying on this panel is the subsystem setting for the Dynamic backout option, so ensure that it is selected for each subsystem that you require it for.

FMNIA188

UNDO not active - The UNDO command is not active because the PSB that your Edit is using has no IO PCB.

You issued the UNDO command. This is a request to back out all the database changes you have made since the last checkpoint. However, IMS cannot back out your changes because the PSB that your Edit is using has no IO PCB.

If you want to use the UNDO command when editing in DLI mode, you must use a PSB that has an IO PCB.

FMNIA189

VSAVE not active - The VSAVE command is only active when the Edit or Browse is using a view.

You issued the VSAVE command. This is a request to save the view that your Edit or Browse is using. However, your request cannot be honored because the Edit or Browse is not using a view.

If you want the Edit/Browse to use a view, return to the Edit/Browse Entry panel and select New or Existing for the View usage.

FMNIA415

Create/Edit failed - Create/Edit failed because DBDLIB &DSN is not a PDS(E). Use option 4.1 or option 4.4 to update the DBDLIBs specified in the template that the view/criteria set was created from, then update the view/criteria set.

The CM command (Create view/criteria set from model) failed because one of the DBDLIB data sets (&DSN) specified in the model view/criteria set is not a PDS(E) or the E command (Edit view/criteria set) failed because one of the DBDLIB data sets (&DSN) specified in the view/criteria set is not a PDS(E).

Use option 4.1 or option 4.4 to correct the DBDLIB data set name specified in the template that the view/criteria set was created from then use option 4.2/4.3 to update the view/criteria set.

FMNIA416

Create/Edit failed - Create/Edit failed because DBDLIB &DSN. is not a loadlib. Use option 4.1or option 4.4 to update the DBDLIBs specified in the template that the view/criteria set was created from, then update the view/criteria set.

The CM command (Create view/criteria set from model) failed because one of the DBDLIB data sets (&DSN) specified in the model view/criteria set is not a loadlib or the E command (Edit view/criteria set) failed because one of the DBDLIB data sets (&DSN) specified in the view/criteria set is not a loadlib.

Use option 4.1 or option 4.4 to correct the DBDLIB data set name specified in the template that the view/criteria set was created from then use option 4.2/4.3 to update the view/criteria set.

FMNIA417

Create/Edit failed - Create/Edit failed because DBDLIB &DSN was not found in the catalog. Use option 4.1 or option 4.4 to update the DBDLIBs specified in the template that the view/criteria set was created from, then update the view/criteria set.

The CM command (Create view/criteria set from model) failed because one of the DBDLIB data sets (&DSN) specified in the model view/criteria set was not found in the catalog or the E command (Edit view/criteria set) failed because one of the DBDLIB data sets (&DSN) specified in the view/criteria set was not found in the catalog.

Use option 4.1 or option 4.4 to correct the DBDLIB data set name in the template that the view/criteria set was created from then use option 4.2/4.3 to update the view/criteria set.

FMNIA453

Not partitioned - Member name specified, but the data set is not partitioned.

A member name was specified with a data set which is not partitioned.

Remove the member name, or verify that the data set was correctly specified and correctly allocated.

FMNIA454

Member &MBR. specified, but &PARM data set &DSN is not partitioned.

The data set specified in the &PARM parameter is not partitioned, but a member name was specified for the data set (either in the &PARM parameter or in the associated member parameter).

Remove the member name from the &PARM parameter, or remove the member parameter specification from the FMNIMSIN input, or verify that the data set was correctly specified and correctly allocated.

FMNIA455

Not partitioned - The data set must be partitioned.

Self explanatory.

Specify a PDS(E).

FMNIA458

Member &MBR. was not found in &PARM data set &DSN.

The member &MBR was not found in the directory of the data set (&DSN) specified in the &PARM parameter.

Specify a member that is in the directory of the data set.

FMNIA459

&PARM data set &DSN is partitioned. You must specify a member.

The data set specified in the &PARM parameter is partitioned, but no member was specified.

Specify the member name either in parenthesis after the data set name or in the associated member parameter, or verify that the data set was correctly specified and correctly allocated.

FMNIA460

Member not found - Member &MBR was not found in data set &DSN.

Self explanatory.

Specify a member that is in the data set.

FMNIA999

File Manager problem - message &MSG not found in table

File Manager cannot find the message number nnnn in the message table. This is probably a File Manager error.

Contact your system support.

FMNIB283

Segment not found - The segment was not found using the specified key values and occurrence numbers.

The key values and occurrence numbers specified on the key specification panel resulted in FM/IMS not finding the segment in the IMS database.

Modify the key values and occurrence numbers to retrieve the require IMS segment.

FMNIB290

PREV limited due to scope - The scope of the PREVIOUS command is limited to the beginning of the current database record

The scope of the records has been limited to only show the segments for a single root segment (database record) by setting the 'Set SCOPE REC' field in 'Edit Options' (option 0.5) or issuing the 'SCOPE REC' or 'SCOPE DBREC' command in the browse/edit session. Hence when scrolling up using the PREVIOUS command you will not be able to scroll up past the root segment or the first segment displayed for the database record (if segments excluded).

To position on a previously displayed record use the KEY command to position on the required segment.

FMNIB291

Top of window reached

The PREVIOUS command was entered and you are currently positioned at the beginning of the database or if you entered key values on the 'Database Positioning' panel you are back at your starting position in the IMS database. Scrolling backwards is not possible.

If you entered key values on the Database positioning panel and want to specify a new starting position you can either return to the 'Database Positioning' panel or enter the KEY command while in the browse/edit session.

FMNIB292

End of database reached

The NEXT command was entered and you are currently positioned at the end of the database, scrolling forwards is not possible.

No action is required.

FMNIB293

Non-replace PCB - The function, which requires Replace permission, cannot be performed with the PCB's PROCOPT.

The Static PSB's PCB for the IMS database being accessed has not got replace permission specified in PCB's PROCOPT parameter. The function using this Static PSB will not be able to update IMS segments.

If the IMS segments are required to be updated, you will need to specify a different PCB for the IMS database with the required permissions either in the same static PSB or different static PSB. If available a Dynamic PSB can be used by the function to access the IMS database, FM/IMS will generate a PSB with the required permissions. To use a dynamic PSB specify 'Dynamic' for the PSB type in System settings (option 0.2).

FMNIB294

Load error: The load file includes a record for index database &DBD ; records for indexes should not be included.

The load file has records which were extracted from an IMS index database. IMS Index databases are not able to loaded in FM/IMS.

No action is required.

FMNIB295

DELIMS/REPLIMS failed with segment &SEGM because PCB &PCBN of PSB &PSB has PROCOPT &POPT.

The DELIMS or REPLIMS function call in the batch IEB job failed as the &PCB PCB of static PSB &PSB did not have delete (for DELIMS) or replace (for REPLIMS) permission for the IMS database specified in the PCB's PROCOPT parameter.

Modify the batch IEB job to specify a PCB (PCBNUM) and static PSB (PSBMEM) with the required permissions for the IMS database. If available a dynamic PSB could be used by the batch IEB job to update the IMS database.

FMNIB296

PSB &PSBMBR. has multiple PCBs for related database &DBD ; specify the PCB you want used in PCBNUM or PCBNAME parameter.

The IMS database extract (IXB) uses a static PSB which has multiple PCBs for the logically related database &DBD and you have not specified a PCB for the PCBNUM or PCBNAME parameters in the FMNIMSIN control cards which references the IMS database &DBD.

Update the PCBNUM or PCBNAME parameter on the FMNIMSIN control card to reference the IMS database &DBD. For more information on these parameters, see Extract (IXB).

FMNIB297

PSB &PSBMBR has multiple PCBs for primary database &DBD ; specify the PCB you want used in PCBNUM or PCBNAME parameter.

The IMS database extract (IXB) uses a static PSB which has multiple PCBs for the primary database &DBD and you have not specified a PCB for the PCBNUM or PCBNAME parameters in the FMNIMSIN control cards which references the IMS database &DBD.

Update the PCBNUM or PCBNAME parameter on the FMNIMSIN control card to reference the IMS database &DBD. For more information on these parameters, see Extract (IXB).

FMNIB298

Load using an alternate processing sequence is not supported.

The PCB for the DBD being loaded using the Static PSB specifies a secondary index (PROCSEQ in the PSB). An alternate process sequence (secondary index) is not allowed when loading an IMS database.

Specify a static PSB/PCB that does not specify a secondary index (PROCSEQ in the PSB) for the IMS databases (including logically related databases) being loaded.

FMNIB532

Function terminated because auditing to SMF failed, BPX1SMF call returned RC=&RC Reason Code=&RC(Dec)

FM/IMS is set up to write audit records to SMF for the current function. A failure occurred while attempting to write an audit record to SMF. The BPX1SMF call resulted in return code &RC and reason code &RC, both expressed in decimal. The current function may be terminated.

This error usually indicates a set-up problem. Possible reason for an auditing failure to SMF are:
  1. The userid does have READ access to the SAF FACILITY class profile BPX.SMF.
  2. The FMN1POPT module does not have a valid number specified for the SMFNO parameter.
Consult the systems programmer for assistance in resolving the cause of the error.

FMNIB835

&CMD not allowed - The &CMD of this segment is not allowed because it may cause a U0828 abend (duplicate segments in a unique secondary index). The &CMD of this segment is allowed when the dynamic backout option on the DLI Mode Settings panel is selected and you use an IMS log.

The insert/repeat (&CMD) is not allowed because you are attempting to insert an IMS segment that is the source for a secondary index and it might create a duplicate index entry.

No action is required.

FMNIB836

&CMD not allowed - The &CMD of this segment is not allowed because it is the target of the secondary index that your Edit is using.

The delete/insert/repeat (&CMD) is not allowed because you are attempting to insert or delete an IMS root segment that is the target for a secondary index or one of its physical parents and it might create a duplicate index entry.

No action is required.

FMNIB837

&CMD not allowed - The &CMD of this segment is not allowed because it is a physical parent of the target of the secondary index that your Edit is using.

The delete/insert/repeat (&CMD) is not allowed because you are attempting to insert or delete an IMS non-root segment that is the target for a secondary index or one of its physical parents and it might create a duplicate index entry.

No action is required.