We have a situation where a job is running, the journal fills up and the job abends and does not give us the ability to perform a Retry once the CHGJRN command is completed. Instead, we are forced to either perform a Dump or Cancel the job. Any ideas why we are not given the option of performing a Retry once the CHGJRN command is completed?
Yes, because the system provides journal options to help you prevent these situations. Look at the Journal Threshold setting options so that you can advise the system admin how full he wants his journal receivers to become along with a peek at the System Managed journal feature so that OS/400 can performing the housekeeping chore automatically when the threshold is reached.Then you won't have to worry about it.
MORE INFORMATION ON THIS TOPIC
Search400.com's targeted search engine: Get relevant information on DB2/400.
The Best Web Links: tips, tutorials and more.
Check out this recent Search400.com Featured Topic: Ask the DB2 UDB doctor .
Dig Deeper on DB2 UDB (universal databases)
Related Q&A from Kent Milligan
Create a host variable of the where in statement on the fly with dynamic SQL. Continue Reading
When working with DB2 files with columns that have both short and long names, there is no option choose which column names are returned via ODBC ... Continue Reading
When developing tables in a parent-child relationship, use a primary key and a foreign key along with a unique ID to make your database easier to ... Continue Reading