Problem
At startup of your CICS® Transaction Server (CICS TS) region, you receive message IXG231I IXGCONN reason 80B. This is followed by message DFHLG0508 log not defined to MVS.
At startup of your CICS® Transaction Server (CICS TS) region, you receive message IXG231I IXGCONN reason 80B. This is followed by message DFHLG0508 log not defined to MVS.
Symptom
You initially set up Logger to use DUMMY logs and now you want to set up real logs. While going through the logger and policy definitions, you found the MVS group made a typo in the stream name. This was subsequently corrected.
After correcting the typo, you still receive the following at startup when attempting to connect to the log:
DFHLG0103I System log (DFHLOG) initialization has started.
IXG231I IXGCONN REQUEST=CONNECT TO LOG STREAM ISP.TST000.TEST000.DFHLOG DID NOT SUCCEED FOR JOB . RETURN CODE: 00000008 REASON CODE: 0000080B DIAG1: 00000008 DIAG2: 0000F801 DIAG3: 05030004 DIAG4: 05020010
DFHLG0508 Log stream ISP.TST000.TEST000.DFHLOG not defined to MVS because model stream SSY6.DFHLOG.MODEL does not exist.
DFHLG0731 A failure has occurred while opening the system log (DFHLOG).DFHDU0303I Transaction Dump Data set DFHDMPA closed.DFHKE1800 ABNORMAL TERMINATION OF CICS IS COMPLETE.
Cause
The STREAMNAME in CICS CEDA definition does not match the LOGSTREAM NAME in MVS definition. Here are the definitions that caused the failure:
MVS Policy using IXCMIAPU:
LOGSTREAM NAME(TST000.TEST000.DFHLOG) STRUCTNAME() LS_DATACLAS()LS_MGMTCLAS() LS_STORCLAS() HLQ(ISP) MODEL(NO)LS_SIZE(12000)STG_MGMTCLAS() STG_STORCLAS() STG_DATACLAS()STG_SIZE(3000)
LOWOFFLOAD(60) HIGHOFFLOAD(80) STG_DUPLEX(YES)
DUPLEXMODE(UNCOND)
RMNAME() DESCRIPTION() RETPD(0) AUTODELETE(NO)
DASDONLY(YES) DIAG(NO) MAXBUFSIZE(65532)
CICS Journal model using CEDA:
CICS Journal model using CEDA:
CEDA View Journalmodel( DFHLOG )
Journalmodel : DFHLOG
Group : LOGSCICS
Description : DEFINE SYSTEM LOG AS MVS
Journalname : DFHLOG
Type : Mvs Mvs | Smf | Dummy
Streamname : ISP.TST000.TEST000.DFHLOG
Resolving the problem
Change the logstream name in the MVS policy to match the streamname in the CEDA Journalmodel.
Once you correct the DASD ONLY CICS Journalmodel definition, the region will start up fine with the expected DFHLG0777 reason 868 message. This message is to be expected at connect time during CICS startup when the staging dataset is being allocated. You may see more than one 868 message depending on staging dataset size.
Change the logstream name in the MVS policy to match the streamname in the CEDA Journalmodel.
Once you correct the DASD ONLY CICS Journalmodel definition, the region will start up fine with the expected DFHLG0777 reason 868 message. This message is to be expected at connect time during CICS startup when the staging dataset is being allocated. You may see more than one 868 message depending on staging dataset size.
沒有留言:
張貼留言