Technical data

Programming Release Notes
6.1 Backup API
6.1.3 Repetitive Calls to BACKUP$START Can Cause an Error
V7.1
Repetitive calls to BACKUP$START can cause the following error:
%BACKUP-F-INSBUFSPACE, insufficient buffer space
The number of repetitive calls completed before receiving this error varies,
depending on the previous backup operations performed.
The workaround for an application that receives this error is to exit the operation
and restart.
6.2 Batch and Print Queues—Terminating Executing Batch Jobs
V6.2
Under the following conditions, the DELETE/ENTRY command may fail to stop
an executing batch job:
• The batch job is a DCL command procedure.
• There is an ON ERROR CONTINUE command (or SET NOON command)
within the command procedure.
The DELETE/ENTRY command causes the job to terminate in phases. A delete_
process AST routine is given in user mode, supervisor mode, and then executive
mode. Because there is a small delay between each mode, it is possible that,
in a batch job, a user-mode image may terminate, and the command procedure
may continue to execute until the supervisor-mode delete_process AST routine is
executed.
The return status of the SYNCHRONIZE command is assumed to contain the
termination status of the target batch job. In addition, command procedures
would normally execute a command such as $ON ERROR THEN CONTINUE or
$SET NOON before issuing the SYNCHRONIZE command. If a DELETE/ENTRY
command is issued to the job executing the SYNCHRONIZE command, the
JBC$_JOBABORT is interpreted as being the termination status of the target
batch job rather than a return status of the SYNCHRONIZE command. The
command procedure then continues to execute for a short period with this
incorrect assumption and performs an operation such as requeuing the target
batch job or incorrectly reporting a failure of the target batch job.
This problem has been corrected for the SYNCHRONIZE command by detecting
this situation and waiting in an exit handler for longer than the delay between
the user-mode and supervisor-mode termination delay.
Any other images that would report the job completion status obtained by the
SJC$_SYNCHRONIZE_JOB function code of the $SNDJBC system service as the
return status of the program should implement logic similar to the following:
1. Declare an exit handler.
2. In the exit handler, implement the following logic:
IF (exit status is JBC$_JOBABORT)
THEN
Wait 10 seconds
ENDIF
6–2 Programming Release Notes