Why does Error 14 in frame 175 at line 321 occur from print jobs

This error occurs during the closing/completion of a print job, where the print job no longer exist.

Example: 

Error 14 in Frame 175 at Line 321
HALT – Program Execution Halted
A:$ = 175,0321
rdb->

This occurs if process ‘A’ deletes a print job, whilst process ‘B’ is updating it. One common cause of this is during the creation of a print job on the secondary system of a failsafe pair such as during the save of a secondary database.

Typically in a failsafe situation, during normal operation an operator will instigate a save of the secondary machine from tlmenu on the primary. The save process, just like any other FILE-SAVE not only updates the STAT-FILE, but one of it’s last jobs is to print the stat-file, causing a pint job to be created on the secondary.

A user on the primary database creates a print job with the same number as one created on the secondary (via the save described above), which is subsequently printed and deleted. This causes a delete image for the print job to be logged and transferred to the secondary machine, which is replayed, deleting the print job on the secondary. The subsequent close of the print job on the secondary created during the save process then aborts with the error above as it is trying to close a print job which no longer exists.

The recommended solution to this is to configure the secondary so that any print job goes back to the primary to be created, which then causes the secondary to receive the creation, thus keeping both primary & secondary spooler jobs in step. This technology is called remote spooling and is setup via ‘tlmenu’.

Back to articles