Task=task_name Pgm=SFMJD001 Insert record failed for record type hex_record_type
Explanation: The agent database interface was unable to successfully insert a new record if type hex_record_type. A snap dump of the record will appear in the SCIOUT DD file with the heading “Record not written to DB”. The cause is usually that the agent lost its connection to the Derby database, although it could be also be caused by an out of space condition or an SQL error. This message will be preceded by several lines of message SFM0341E that contain detailed information about the SQL request that failed. The same SQL message lines will appear in the JAVAMSG DD spool file. If this error is due to a dropped database connection, it will be retried indefinitely until the database connection is re-established.
| Record type (hex) | Database table |
| 01 and 08 | FTP_SESSION_SUMMARY |
| 02 and 09 | FTP_TRANSFER |
| 03 | FTP_SESSION_DETAIL |
| 04 | FTP_SUMMARY_ACTIVITY |
| 05 | MESSAGELOG |
| 06 | AGENT_CONFIG |
| 07 | LICENSE_CODE |
| 0A and 0C | REQUEST |
| 0E | AGENT_HEARTBEAT |
| 0F | FTP_LOGIN_FAILURE |
| 10 | FTP_RENAME |
| 11 | FTP_DELETE |
Action: Determine why the Derby database is down or why agent_name does not have a network path to the database. Also, check the USS file system where the Derby database files reside to determine if it has free space available. One way to check the free space is to use the command df -Pk mountpoint on the USS command line replacing mountpoint with the actual mountpoint for the Derby file system.