File Manager IMS Messages

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.

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

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.

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.

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.

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

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

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.

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

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.

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.

Self explanatory.

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

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.

Self explanatory.

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

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

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

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

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

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).

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.

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.

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.

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.

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

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

Self explanatory.

Self explanatory.

Self explanatory.

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

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

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

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

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

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

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

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

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

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

Self explanatory.

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.

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

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.

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.

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.

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.

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.

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.

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

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

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.

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

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.

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

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

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.

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.

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.

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.

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.

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.

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

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

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.

Self explanatory.

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.

Self explanatory.

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

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

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

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.

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

Self explanatory.

Self explanatory.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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

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.

&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.

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.

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.

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.

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.

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.

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.

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.

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.

You left the PCB Selection panel without selecting a PCB.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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).

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.

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.

A member name was specified with a data set which 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).

Self explanatory.

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

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

Self explanatory.

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

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

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).

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.

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

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.

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

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.

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.

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.

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.

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.

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.

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.

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.