The message extraction works, we have not picked up a message with the replacement data added but that should only affect the content we parse. The program now correctly parses a message with the Format Control Characters and ensures the SMTP line length does not exceed the maximum allowed (78). Once the programs are put into the production suite we should be able to see the replacement variables correctly filled in.
Change not applied or removed to object type *&5, reason code &6.
Cause . . . . . : The operation to apply or remove journaled entries
failed at sequence number &4 with reason code &6 and additional entry code &14. The object associated with the entry is &1 in library &2 of type *&5 member &3, or has file ID &15 and path &16. &9 entries were successfully applied or removed.The additional entry code is &14. If the additional entry code is ‘1’, then there were additional entries to process for this object.
If *N or hex zero appears for any fields, the information is not available or does not apply.
Reason codes:
X’00’ – Refer to other messages in the joblog.
X’01’, X’02’ – An attempt was made to update a record that does not exist in the file.
X’03’ – Either an attempt was made to insert over an existing record, or an attempt was made to insert a record beyond the last record in the file.
X’04’, X’05’ – An attempt was made to delete a record that does not exist in the file.
X’06’ – An attempt was made to apply an update to a record that does not match the current version of the record in the file.
X’08’ – A before image entry was required to perform the operation but the journal does not contain the before image entry.
X’09’ – Journal entry &4 describes a valid change to the object, but the APYJRNCHG and RMVJRNCHG commands do not process the change described by that entry.
X’0A’ – Attempted to exceed the maximum number of records for the object.
X’0B’ – The length of the journal entry does not match the length of the entry expected for the operation.
X’0C’ – An error occurred which is described by error number &8. Display message CPE&8 for further explanation of the error number.
X’0D’ – An error occurred which is described by the error message
identifier: &7.X’0E’ – A timeout occurred while the operating system was attempting to apply the journal entry.
X’0F’ – The specified start of the apply or remove is not at a commit boundary.
X’10’ – An unexpected error occurred. Retry the APYJRNCHG with the
OBJERROPT(*END) option to get more detail about the failure.X’11’ – Start of apply specified from last save entry, save entry not found at starting sequence number.
X’13’ – Tried to dequeue a message that was not in the data queue
X’14’ – Key length or message length does not match the data queue attributes.
X’15’ – Data queue inconsistent with journal
X’16’ – Cannot apply to data queue
X’17’ – Data queue in use, cannot start apply
X’18’ – Data queue has changed since last restore, cannot start apply
X’19’ – Cannot apply data queue entries from releases prior to V5R4M0
Recovery . . . : Use the Display Journal (DSPJRN) command to identify
the operation being performed by journal entry &4 from journal &10 in library
&11 of receiver &12 in library &13.The apply or remove operation may have made changes to the specified objects.
Use DSPMSGD CPI7018 to refer to the specific recovery instructions for reason code &
6
As we mentioned on the previous post, the extraction of the messages will be automated using the technology developed for the RAP product so the only interface we still need to build is the ability to set the message types and severity you want to monitor for etc. Then we should have a process whereby the RAP product will be able to notify the users when any errors or problems arise…