Object server databases initialized without prerequisite library server work

Answer

Here are the meanings of the errors you received:

• FRN7667A means the library server could not talk to the object server.
• -204 refers to a bind problem.
• "GetNetTable(): FRNNETT file Read error" means the program FRNMHLD5 cannot read the file referenced by the //FRNNETT DD statement.

Make sure that you have provided a network table file in your CICS JCL. In this example, it is:
//FRNNETT DD DISP=SHR,DSN=?FRN?.FRNNETT//*

Make sure that you included the FRNNETT entry in your DCT table.

You need a network table dataset for the library client to communicate with the other machine.

To run the FRNMHLD5 job, you must have a library client on your Content Manager for OS/390 system that will interface with the library server. Look at the error message you are getting; the DELE transaction is calling on the FRNMLCII, which is the library client. Within the JCL that you use to run the library client you must also specify an FRNNETT DD pointing to a dataset. After this, you should be able to run the FRNMHLD5 job.

If the object server on which this object used to be stored no longer exists (but the object server code still exists in the library server database), then the delete request will be rejected. It will be rejected because the library server will try to contact the object server before it sends the delete request to the object server. The contact will fail and the delete request will be rejected.

To solve this problem, Content Manager has modified the library server code in PTF UQ44129. With UQ44129, if the transaction ID is FRNB, then for a delete request, the library server will bypass the routine to "contact and send the request to object server." The library server will delete the item and all the related data of this object without checking whether the object server is up.

To use the FRNB transaction, you must:

1. Add an FRNB transaction (copy from the regular FRNI transaction) in the CICS CSD entry.
2. Create an FRNB (again copy from FRNI) configuration via SystemAdmin Client.
• If you want to run the client application on the workstation (to send the delete without object server involved), in the OS/390 library server entry in the FRNOLINT.TBL, change TP = FRNI to TP = FRNB. This must be performed on the workstation which will perform this delete.
  
  After you clean up all the items and related data of non-existing objects, change FRNB back to FRNI so this workstation will continue to use the normal FRNI transaction.
• If you want to run the client application on the OS/390 (to send the delete without object server involved), you must change FRNI to FRNB as the transaction ID of library server. This must be done in the FRNNETT network table used by 390 library client.

The FRNMHLD5 information states that you must have a library client running on MVS for OS/390 to interface with the library server. You do not have to use OS/390 library client to delete an item for an object that no longer exists in OAM, or to delete an object server that no longer exists. The only reason to use the OS/390 library client batch delete FRNMHLD5 is to improve performance. For example, you might have to delete or clean up large amounts of data every day, so you would want to run the OS/390 client application FRNMHLD5 (which issues the delete request to the library server) on the OS/390 to eliminate the overhead of send/receive between the workstation and OS/390.

• The FRNNETT is used by the OS/390 library client, so the library server name and IP address are needed in the FRNNETT file.
• You can install the OS/390 library client in the same CICS region or a different CICS region than that of your OS/390 library server, but the OS/390 library client still needs to know whether the library server is remote or local.
• You do not need to specify the object server name in the FRNNETT. In FRNNETT, the first line identifies the OS/390 library client, the second line identifies the library server.
  

Reminder: You need to switch FRNB back to FRNI so that you can log on via the Client Application. That is, change the FRNOLINT.TBL to include TP = FRNI. If you forgot to make this switch, you might get error message "FRN6740A: The logon was not successful becuase of error 6288."

If you continue to have problems, refer to your LibSrv CICS logs for a security violation for transaction FRNB. It is possible that transaction FRNB was not defined to your security system.

If this is the case, define FRNB with the same properties that are used for FRNI. Then recycle the LibSrv CICS region, and change the FRNOLINT.TBL to include TP = FRNB on one workstation. You should be able to log on to the Client Application and be able to delete specific LibSrv item information for objects that are stored in the ObjSrv.

Finally, the LibClient *.SFRNLMD4 load library might not have been included originally in the LibSrv CICS region if you chose not to use LibClient on OS/390. If you add *.SFRNLMD4, transaction FRNB should be activated (FRNT 20020411112104 FRNMHBLT: Enabling transaction FRNB).