Symptom
- System is failing to start.
- Only SAPSTART jobs are visible in WRKSBS.
- SAPSTART jobs are in status MSGW
- Option 7 when selecting the SAPSTARTjob reveals the following:
-
Message ID . . . . . . : CPA7090 Severity . . . . . . . : 99
Message type . . . . . : Inquiry
Date sent . . . . . . : 01/10/20 Time sent . . . . . . : 06:14:32
Message . . . . : Entry not journaled to journal QSQJRN in R3<SID>DATA. (C R)
Cause . . . . . : The entry was not journaled into receiver QSQJRN0516 in
library R3<SID>JRN for journal QSQJRN in library R3<SID>DATA because of reason
code 1. The object associated with this entry is *N in library *N of type
**N member *N, or has file ID X'00000000000000000000000000000000' and path
*N. If *N or hex zero appears, information is not available or does not
apply.
Reason code definitions:
1 -- Space for entry cannot be allocated on journal receiver.
2 -- Journal is damaged.
3 -- Attached receiver is damaged. - The joblog (option 10 in the job's menu) reveals the following. It is important the reason code is 1:
-
Message . . . . : Entry not journaled to journal QSQJRN. Reason code 1.
Cause . . . . . : The entry was not journaled into receiver QSQJRNxxxx in
library R3<SID>JRN for journal QSQJRN in library R3<SID>DATA because of reason
code 1. The object associated with this entry is *N in library *N of type
**N member *N, or has file ID X'00000000000000000000000000000000' and path
*N. If *N or hex zero appears, information is not available or does not
apply.
Reason code definitions:
1 -- Space for entry cannot be allocated on journal receiver.Message ID . . . . . . : CPF7003
- WRKJRNA jrn(R3<SID>DATA/QSQJRN) should show a huge journal reciever that will not detach:
-
Journal . . . . . . : QSQJRN Library . . . . . . : R3<SID>DATA
Total size of receivers (in kilobytes) . . . . . . . . . . . : 1098764900 <<this figure may vary.
Read more...
Environment
Any SAP system on IBM i.
Product
Keywords
as/400, ibm i, iseries, startsap, stopsap, journals, journalling , KBA , BC-DB-DB4 , DB2 for AS/400 , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.