|  | 
 
  
    | RSS Feed - WebSphere MQ Support | RSS Feed - Message Broker Support |  
 
  
	|    |  |  
  
	| MQ LOG FULL ISSUE - LAST AVAILABLE ACTIVE LOG DATA SET | « View previous topic :: View next topic » |  
  	| 
		
		
		  | Author | Message |  
		  | migz0901 | 
			  
				|  Posted: Mon Dec 05, 2016 7:04 am    Post subject: MQ LOG FULL ISSUE - LAST AVAILABLE ACTIVE LOG DATA SET |   |  |  
		  | Apprentice
 
 
 Joined: 01 Nov 2012Posts: 28
 
 
 | 
			  
				| Hi Guys, 
 I have problems with our log datasets, they are becoming full then archive log issued and offloading takes place and switched to new 2 last active datasets, reason same problem occur.
 
 How to correct our current log situation?
 
 MSTR log...
 
 22.33.48 STC01435  CSQJ110E +MQP4 LAST COPY 1 ACTIVE LOG DATA SET IS 70 PERCENT
 22.35.26 STC01435  CSQJ110E +MQP4 LAST COPY 2 ACTIVE LOG DATA SET IS 70 PERCENT
 22.46.38 STC01435  CSQJ110E +MQP4 LAST COPY 1 ACTIVE LOG DATA SET IS 75 PERCENT
 22.47.56 STC01435  CSQJ110E +MQP4 LAST COPY 2 ACTIVE LOG DATA SET IS 75 PERCENT
 
 
 Display log results......
 22.50.23 STC01435  CSQJ322I +MQP4 DISPLAY LOG report ...  224
 224             Parameter   Initial value          SET value
 224             ----------- ---------------------- ----------------------
 224             INBUFF      60
 224             OUTBUFF     4000
 224             MAXRTU      2
 224             MAXARCH     500
 224             TWOACTV     YES
 224             TWOARCH     YES
 224             TWOBSDS     YES
 224             OFFLOAD     YES
 224             MAXCNOFF    31
 224             WRTHRSH     20
 224             DEALLCT     0
 224             COMPLOG     NONE
 224             End of LOG report
 22.50.23 STC01435  CSQJ370I +MQP4 LOG status report ...  225
 225             Copy %Full DSName
 225              1     37  MQSP.MQP4.LOGCOPY1.DS01
 225              2     37  MQSP.MQP4.LOGCOPY2.DS01
 225             Restarted at 2016-12-04 03:52:04 using RBA=0000040596A62000
 225             Latest RBA=00000406F8AA807C
 225             Offload task is BUSY
 225             Full logs to offload - 6 of 8
 22.50.23 STC01435  CSQ9022I +MQP4 CSQJC001 ' DISPLAY LOG' NORMAL COMPLETION
 
 
 display archive results...
 
 
 22.50.13 STC01435  CSQJ322I +MQP4 DISPLAY ARCHIVE report ...  203
 203             Parameter   Initial value          SET value
 203             ----------- ---------------------- ----------------------
 203             UNIT        STAPE
 203             UNIT2
 203             ALCUNIT     BLK
 203             PRIQTY      4320
 203             SECQTY      540
 203             BLKSIZE     28672
 203             ARCPFX1     MQSP.MQP4.ARCHLOG1
 203             ARCPFX2     MQSP.MQP4.ARCHLOG2
 203             TSTAMP      NO
 203             ARCRETN     32
 203             ARCWTOR     NO
 203             ARCWRTC     1 ,3 ,4
 203             CATALOG     YES
 203             COMPACT     NO
 203             PROTECT     NO
 203             QUIESCE     5
 203             End of ARCHIVE report
 22.50.13 STC01435  CSQJ325I +MQP4 ARCHIVE tape unit report ...  204
 204             Addr St CorrelID VolSer DSName
 204             ---- -- -------- ------ -------------------------------------
 204             No tape archive reading activity
 204             End of tape unit report
 22.50.13 STC01435  CSQ9022I +MQP4 CSQJC001 ' DISPLAY ARCHIVE' NORMAL COMPLETION
 22.50.13 STC01435  CSQJ325I +MQP4 ARCHIVE tape unit report ...  204
 204             Addr St CorrelID VolSer DSName
 204             ---- -- -------- ------ -------------------------------------
 204             No tape archive reading activity
 204             End of tape unit report
 22.50.13 STC01435  CSQ9022I +MQP4 CSQJC001 ' DISPLAY ARCHIVE' NORMAL COMPLETION
 
 
 How to fix these....
 
 225             Offload task is BUSY         >> normal is available
 225             Full logs to offload - 6 of 8       -- normal is zero.
 
 
 
 Hope to hear from you guys soon...before real problems happened.
 
 Many thanks,
 Migz0901
 |  |  
		  | Back to top |  |  
		  |  |  
		  | Vitor | 
			  
				|  Posted: Mon Dec 05, 2016 7:07 am    Post subject: Re: MQ LOG FULL ISSUE - LAST AVAILABLE ACTIVE LOG DATA SET |   |  |  
		  |  Grand High Poobah
 
 
 Joined: 11 Nov 2005Posts: 26093
 Location: Texas, USA
 
 | 
			  
				| 
   
	| migz0901 wrote: |  
	| How to correct our current log situation? |  
 Ensure the logs are sized appropriately.
 
 Ensure applications are using units of work appropriately.
 _________________
 Honesty is the best policy.
 Insanity is the best defence.
 |  |  
		  | Back to top |  |  
		  |  |  
		  | bruce2359 | 
			  
				|  Posted: Mon Dec 05, 2016 7:17 am    Post subject: |   |  |  
		  |  Poobah
 
 
 Joined: 05 Jan 2008Posts: 9486
 Location: US: west coast, almost. Otherwise, enroute.
 
 | 
			  
				| Moving this to z/OS MQ forum. _________________
 I like deadlines. I like to wave as they pass by.
 ב''ה
 Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
 |  |  
		  | Back to top |  |  
		  |  |  
		  | bruce2359 | 
			  
				|  Posted: Mon Dec 05, 2016 7:26 am    Post subject: |   |  |  
		  |  Poobah
 
 
 Joined: 05 Jan 2008Posts: 9486
 Location: US: west coast, almost. Otherwise, enroute.
 
 | 
			  
				| Is this a new issue?  If so, what has changed?  If logging was behaving well previously, and suddenly misbehaves, I'd suspect an application (new or updated) is the cause. 
 What are the sizes of your log datasets?  Look at the MQ startup SYSLOG entries.  And/or use ISPF panels or MQSC commands to display logs.  Post results here.
 _________________
 I like deadlines. I like to wave as they pass by.
 ב''ה
 Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
 |  |  
		  | Back to top |  |  
		  |  |  
		  | migz0901 | 
			  
				|  Posted: Mon Dec 05, 2016 7:58 am    Post subject: |   |  |  
		  | Apprentice
 
 
 Joined: 01 Nov 2012Posts: 28
 
 
 | 
			  
				| We have applied RSU1607 for zOS MQ last weekend and the log issue occurs... I have shutdown the MQ started stc with mode(force) due to it cant shutdown normally. 
 But in other lpar we also applied the RSU1607 but no issue with MQ.
 
 here's the log details....
 
 - Enter "/" to select action                        Tracks %Used   XT
 -----------------------------------------------------------------------
 MQSP.MQP4.LOGCOPY1.DS01
 MQSP.MQP4.LOGCOPY1.DS01.DATA                        15000    ?     1
 MQSP.MQP4.LOGCOPY1.DS02
 MQSP.MQP4.LOGCOPY1.DS02.DATA                        15000    ?     1
 MQSP.MQP4.LOGCOPY1.DS03
 MQSP.MQP4.LOGCOPY1.DS03.DATA                        15000    ?     1
 MQSP.MQP4.LOGCOPY1.DS04
 MQSP.MQP4.LOGCOPY1.DS04.DATA                        15000    ?     1
 MQSP.MQP4.LOGCOPY2.DS01
 MQSP.MQP4.LOGCOPY2.DS01.DATA                        15000    ?     1
 MQSP.MQP4.LOGCOPY2.DS02
 MQSP.MQP4.LOGCOPY2.DS02.DATA                        15000    ?     1
 MQSP.MQP4.LOGCOPY2.DS03
 MQSP.MQP4.LOGCOPY2.DS03.DATA                        15000    ?     1
 MQSP.MQP4.LOGCOPY2.DS04
 MQSP.MQP4.LOGCOPY2.DS04.DATA                        15000    ?     1
 
 
 
 
 CSQJ322I +MQP4 DISPLAY LOG report ...  985
 Parameter   Initial value          SET value
 ----------- ---------------------- ----------------------
 INBUFF      60
 OUTBUFF     4000
 MAXRTU      2
 MAXARCH     500
 TWOACTV     YES
 TWOARCH     YES
 TWOBSDS     YES
 OFFLOAD     YES
 MAXCNOFF    31
 WRTHRSH     20
 DEALLCT     0
 COMPLOG     NONE
 End of LOG report
 Copy %Full DSName
 1     67  MQSP.MQP4.LOGCOPY1.DS01
 2     67  MQSP.MQP4.LOGCOPY2.DS01
 Restarted at 2016-12-04 03:52:04 using RBA=0000040596A62000
 Latest RBA=0000040705C601F6
 Offload task is BUSY
 Full logs to offload - 6 of 8
 CSQ9022I +MQP4 CSQJC001 ' DIS LOG' NORMAL COMPLETION
 
 
 
 I can not issue the archive log command due to the current logs are the last active log....
 
 
 thanks,
 
  |  |  
		  | Back to top |  |  
		  |  |  
		  | fjb_saper | 
			  
				|  Posted: Mon Dec 05, 2016 8:38 am    Post subject: |   |  |  
		  |  Grand High Poobah
 
 
 Joined: 18 Nov 2003Posts: 20767
 Location: LI,NY
 
 | 
			  
				| You need to find out why your offload task is busy... Is it waiting on (catalogued) tapes?
  _________________
 MQ & Broker admin
 |  |  
		  | Back to top |  |  
		  |  |  
		  | bruce2359 | 
			  
				|  Posted: Mon Dec 05, 2016 1:22 pm    Post subject: |   |  |  
		  |  Poobah
 
 
 Joined: 05 Jan 2008Posts: 9486
 Location: US: west coast, almost. Otherwise, enroute.
 
 | 
			  
				| 
   
	| migz0901 wrote: |  
	| But in other lpar we also applied the RSU1607 but no issue with MQ. |  That seems to narrow it down to something application-specific to that LPAR.
 
 I've seen this before when a developer created one enormous Unit of Work that attempted to span a 300,000 record file update.  (It should have been 300,000 individual UofW's.)  Filled up the logs, apps received the no-log-space-available r/c, and the log offloads couldn't keep up.
 
 15000 tracks = 1000 cyl x 4 log segments.  That's a 3390-mod 3, and a bit more.  About 4GB of log space, if my memory and math are still working.
 
 What apps are running when you run out of log space?  What size messages are they MQPUTting?
 _________________
 I like deadlines. I like to wave as they pass by.
 ב''ה
 Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
 |  |  
		  | Back to top |  |  
		  |  |  
		  | migz0901 | 
			  
				|  Posted: Mon Dec 05, 2016 5:46 pm    Post subject: |   |  |  
		  | Apprentice
 
 
 Joined: 01 Nov 2012Posts: 28
 
 
 | 
			  
				| Hello, 
 I have reviewed again the MSTR stc and found that there was unsuccessful offloading task after the QUIESCING FOR ARCHIVE LOG COMMAND...
 
 How to stop or cancel this outstanding task....?
 
 
 00.02.05 STC01435 ---- MONDAY,    05 DEC 2016 ----
 00.02.05 STC01435  CSQY220I +MQP4 CSQSCTL Queue manager storage usage:  887
 887             local storage: used 271MB, free 1204MB: above bar: used 231M
 887             1GB
 00.30.57 STC01435  CSQJ310I +MQP4 QUIESCING FOR ARCHIVE LOG COMMAND WITH  755
 755             WAIT(NO) STARTED FOR MAXIMUM OF   5 SECONDS
 00.30.57 STC01435  CSQJ002I +MQP4 END OF ACTIVE LOG DATA SET  756
 756             DSNAME=MQSP.MQP4.LOGCOPY1.DS03, STARTRBA=00000405ECCC2000
 756             ENDRBA=000004060CB3CFFF
 00.30.57 STC01435  CSQJ001I +MQP4 CURRENT COPY 1 ACTIVE LOG DATA SET IS  757
 757             DSNAME=MQSP.MQP4.LOGCOPY1.DS04, STARTRBA=000004060CB3D000
 757             ENDRBA=0000040638A5CFFF
 00.30.57 STC01435  CSQJ002I +MQP4 END OF ACTIVE LOG DATA SET  758
 758             DSNAME=MQSP.MQP4.LOGCOPY2.DS03, STARTRBA=00000405ECCC2000
 758             ENDRBA=000004060CB3CFFF
 00.30.57 STC01435  CSQJ001I +MQP4 CURRENT COPY 2 ACTIVE LOG DATA SET IS  759
 759             DSNAME=MQSP.MQP4.LOGCOPY2.DS04, STARTRBA=000004060CB3D000
 759             ENDRBA=0000040638A5CFFF
 00.30.57 STC01435  CSQJ311I +MQP4 LOG ARCHIVE (OFFLOAD) TASK INITIATED
 00.30.57 STC01435  CSQJ312I +MQP4 ARCHIVE LOG QUIESCE ENDED, UPDATE  761
 761             ACTIVITY IS NOW RESUMED
 00.30.57 STC01435  CSQP018I +MQP4 CSQPBCKW CHECKPOINT STARTED FOR ALL BUFFER PO
 00.30.57 STC01435  +MQP4 DISPLAY CONN(*) TYPE(CONN) ALL WHERE(UOWSTATE EQ UNRES
 00.30.57 STC01435  CSQP019I +MQP4 CSQPDWP2 CHECKPOINT COMPLETED FOR  764
 764             BUFFER POOL 1, 0 PAGES WRITTEN
 00.30.57 STC01435  CSQM297I +MQP4 CSQMDRTC NO CONN FOUND MATCHING REQUEST CRITE
 00.30.57 STC01435  CSQ9022I +MQP4 CSQMDRTC ' DISPLAY CONN' NORMAL COMPLETION
 00.30.57 STC01435  CSQP019I +MQP4 CSQPDWP2 CHECKPOINT COMPLETED FOR  767
 767             BUFFER POOL 3, 31 PAGES WRITTEN
 00.30.57 STC01435  CSQP019I +MQP4 CSQPDWP2 CHECKPOINT COMPLETED FOR  768
 768             BUFFER POOL 2, 49 PAGES WRITTEN
 00.30.57 STC01435  CSQP019I +MQP4 CSQPDWP2 CHECKPOINT COMPLETED FOR  769
 769             BUFFER POOL 0, 33 PAGES WRITTEN
 00.30.57 STC01435  CSQP021I +MQP4 Page set 0 new media recovery  770
 770             RBA=00000405FC6E156C, checkpoint RBA=00000405FC6E156C
 00.30.57 STC01435  CSQP021I +MQP4 Page set 1 new media recovery  771
 771             RBA=00000405F814F2FA, checkpoint RBA=00000405F814F2FA
 00.30.57 STC01435  CSQP021I +MQP4 Page set 2 new media recovery  772
 772             RBA=000004060CB3E96D, checkpoint RBA=000004060CB3E96D
 00.30.57 STC01435  CSQP021I +MQP4 Page set 3 new media recovery  773
 773             RBA=00000405F950AA9C, checkpoint RBA=00000405F950AA9C
 00.30.57 STC01435  CSQP021I +MQP4 Page set 4 new media recovery  774
 774             RBA=00000405FBCA3580, checkpoint RBA=00000405FBCA3580
 00.48.43 STC01435  CSQJ110E +MQP4 LAST COPY 1 ACTIVE LOG DATA SET IS 5 PERCENT
 00.51.13 STC01435  CSQJ110E +MQP4 LAST COPY 2 ACTIVE LOG DATA SET IS 5 PERCENT
 01.02.05 STC01435  CSQY220I +MQP4 CSQSCTL Queue manager storage usage:  897
 897             local storage: used 271MB, free 1204MB: above bar: used 231M
 897             1GB
 01.15.17 STC01435  CSQJ110E +MQP4 LAST COPY 1 ACTIVE LOG DATA SET IS 10 PERCENT
 01.19.44 STC01435  CSQJ110E +MQP4 LAST COPY 2 ACTIVE LOG DATA SET IS 10 PERCENT
 01.49.00 STC01435  CSQJ110E +MQP4 LAST COPY 1 ACTIVE LOG DATA SET IS 15 PERCENT
 
 
 
 Thanks
  |  |  
		  | Back to top |  |  
		  |  |  
		  | bruce2359 | 
			  
				|  Posted: Mon Dec 05, 2016 8:28 pm    Post subject: |   |  |  
		  |  Poobah
 
 
 Joined: 05 Jan 2008Posts: 9486
 Location: US: west coast, almost. Otherwise, enroute.
 
 | 
			  
				| 
   
	| migz0901 wrote: |  
	| ...there was unsuccessful offloading task after the QUIESCING FOR ARCHIVE LOG COMMAND... |  Please post the error message.
 
 Also, please post the complete SYSLOG stuff.  What you've posted is incomplete - truncated at the right edge.
 _________________
 I like deadlines. I like to wave as they pass by.
 ב''ה
 Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
 |  |  
		  | Back to top |  |  
		  |  |  
		  | migz0901 | 
			  
				|  Posted: Mon Dec 05, 2016 10:33 pm    Post subject: |   |  |  
		  | Apprentice
 
 
 Joined: 01 Nov 2012Posts: 28
 
 
 | 
			  
				| Hi, 
 The last active log become full then offloading is still happening and I am surprise log switched......  then started to become full again.... then process repeats..  but I only have the last active log available...
 
 
 
 STC01435  CSQJ110E +MQP4 LAST COPY 1 ACTIVE LOG DATA SET IS 85 PERCENT FULL
 STC01435  CSQJ110E +MQP4 LAST COPY 2 ACTIVE LOG DATA SET IS 85 PERCENT FULL
 STC01435  CSQJ110E +MQP4 LAST COPY 1 ACTIVE LOG DATA SET IS 90 PERCENT FULL
 STC01435  CSQJ110E +MQP4 LAST COPY 2 ACTIVE LOG DATA SET IS 90 PERCENT FULL
 STC01435  CSQJ110E +MQP4 LAST COPY 1 ACTIVE LOG DATA SET IS 95 PERCENT FULL
 STC01435  CSQJ110E +MQP4 LAST COPY 2 ACTIVE LOG DATA SET IS 95 PERCENT FULL
 STC01435  CSQJ002I +MQP4 END OF ACTIVE LOG DATA SET  734
 DSNAME=MQSP.MQP4.LOGCOPY1.DS03, STARTRBA=000004074051D000
 ENDRBA=000004076C43CFFF
 STC01435 *CSQJ004I +MQP4 ACTIVE LOG COPY 1 INACTIVE, LOG IN  735
 SINGLE MODE, ENDRBA=000004076C43CFFF
 STC01435  CSQJ002I +MQP4 END OF ACTIVE LOG DATA SET  736
 DSNAME=MQSP.MQP4.LOGCOPY2.DS03, STARTRBA=000004074051D000
 ENDRBA=000004076C43CFFF
 STC01435 *CSQJ111A +MQP4 OUT OF SPACE IN ACTIVE LOG DATA SETS
 STC01435  CSQP018I +MQP4 CSQPBCKW CHECKPOINT STARTED FOR ALL BUFFER POOLS
 STC01435  +MQP4 DISPLAY CONN(*) TYPE(CONN) ALL WHERE(UOWSTATE EQ UNRESOLVED)
 STC01435  CSQP019I +MQP4 CSQPDWP2 CHECKPOINT COMPLETED FOR  740
 BUFFER POOL 1, 0 PAGES WRITTEN
 STC01435  CSQM297I +MQP4 CSQMDRTC NO CONN FOUND MATCHING REQUEST CRITERIA
 STC01435  CSQ9022I +MQP4 CSQMDRTC ' DISPLAY CONN' NORMAL COMPLETION
 STC01435  IEF233D M 03A0,PRIVAT,SL,MQP4MSTR,MQP4MSTR,  743
 MQSP.MQP4.ARCHLOG1.B0008228,
 OR RESPOND TO IEF455D MESSAGE
 STC01435  IECTMS9 03A0,797440,MQP4MSTR,SYS00023,07/01/2017,00001,ARCHLOG1.B0008
 STC01435  IEC705I TAPE ON 03A0,797440,SL,NOCOMP,MQP4MSTR,MQP4MSTR,MQSP.MQP4.ARC
 STC01435  IEC205I SYS00023,MQP4MSTR,MQP4MSTR,FILESEQ=1, COMPLETE VOLUME LIST,
 DSN=MQSP.MQP4.ARCHLOG1.B0008228,VOLS=797440,TOTALBLOCKS=13
 STC01435  IECTMS9 03A0,797440,MQP4MSTR,SYS00023,07/01/2017,00002,ARCHLOG1.A0008
 STC01435  IEF233D M 03A5,PRIVAT,SL,MQP4MSTR,MQP4MSTR,  753
 MQSP.MQP4.ARCHLOG2.B0008228,
 OR RESPOND TO IEF455D MESSAGE
 STC01435  IECTMS9 03A5,769581,MQP4MSTR,SYS00024,07/01/2017,00001,ARCHLOG2.B0008
 STC01435  IEC705I TAPE ON 03A5,769581,SL,NOCOMP,MQP4MSTR,MQP4MSTR,MQSP.MQP4.ARC
 STC01435  IEC205I SYS00024,MQP4MSTR,MQP4MSTR,FILESEQ=1, COMPLETE VOLUME LIST,
 DSN=MQSP.MQP4.ARCHLOG2.B0008228,VOLS=769581,TOTALBLOCKS=13
 STC01435  IECTMS9 03A5,769581,MQP4MSTR,SYS00024,07/01/2017,00002,ARCHLOG2.A0008
 STC01435  IEC205I SYS00023,MQP4MSTR,MQP4MSTR,FILESEQ=2, COMPLETE VOLUME LIST,
 DSN=MQSP.MQP4.ARCHLOG1.A0008228,VOLS=797440,TOTALBLOCKS=25715
 STC01435  CSQJ003I +MQP4 FULL ARCHIVE LOG VOLUME  765
 DSNAME=MQSP.MQP4.ARCHLOG1.A0008228, STARTRBA=00000406BC7BD000
 ENDRBA=00000406E86DCFFF, STARTTIME=D1BFC61E8EC1 ENDTIME=D1C003251E56,
 UNIT=STAPE, COPY1VOL=797440, VOLSPAN=NO CATLG=YES
 STC01435  IEF234E K 03A0,797440,PVT,MQP4MSTR,MQP4MSTR
 STC01435  TMS014  IEF234E K 03A0,797440,PVT,MQP4MSTR,MQP4MSTR
 STC01435  IEC205I SYS00024,MQP4MSTR,MQP4MSTR,FILESEQ=2, COMPLETE VOLUME LIST,
 DSN=MQSP.MQP4.ARCHLOG2.A0008228,VOLS=769581,TOTALBLOCKS=25715
 STC01435  CSQJ003I +MQP4 FULL ARCHIVE LOG VOLUME  771
 DSNAME=MQSP.MQP4.ARCHLOG2.A0008228, STARTRBA=00000406BC7BD000
 ENDRBA=00000406E86DCFFF, STARTTIME=D1BFC61E8EC1 ENDTIME=D1C003251E56,
 UNIT=STAPE, COPY2VOL=769581, VOLSPAN=NO CATLG=YES
 STC01435  IEF234E K 03A5,769581,PVT,MQP4MSTR,MQP4MSTR
 STC01435  TMS014  IEF234E K 03A5,769581,PVT,MQP4MSTR,MQP4MSTR
 STC01435  CSQJ139I +MQP4 LOG OFFLOAD TASK ENDED
 STC01435  CSQJ005I +MQP4 ACTIVE LOG COPY 1 IS ACTIVE, LOG IN  780
 DUAL MODE, STARTRBA=000004076C43D000
 STC01435  CSQJ001I +MQP4 CURRENT COPY 1 ACTIVE LOG DATA SET IS  781
 DSNAME=MQSP.MQP4.LOGCOPY1.DS04, STARTRBA=000004076C43D000
 ENDRBA=000004079835CFFF
 STC01435  CSQJ001I +MQP4 CURRENT COPY 2 ACTIVE LOG DATA SET IS  782
 DSNAME=MQSP.MQP4.LOGCOPY2.DS04, STARTRBA=000004076C43D000
 ENDRBA=000004079835CFFF
 STC01435  CSQP019I +MQP4 CSQPDWP2 CHECKPOINT COMPLETED FOR  783
 BUFFER POOL 2, 23 PAGES WRITTEN
 STC01435  CSQP019I +MQP4 CSQPDWP2 CHECKPOINT COMPLETED FOR  784
 BUFFER POOL 0, 30 PAGES WRITTEN
 STC01435  CSQP019I +MQP4 CSQPDWP2 CHECKPOINT COMPLETED FOR  785
 BUFFER POOL 3, 28 PAGES WRITTEN
 STC01435  CSQP021I +MQP4 Page set 0 new media recovery  786
 RBA=000004075E9440A0, checkpoint RBA=000004075E9440A0
 STC01435  CSQP021I +MQP4 Page set 1 new media recovery  787
 RBA=00000407583D5071, checkpoint RBA=00000407583D5071
 STC01435  CSQP021I +MQP4 Page set 2 new media recovery  788
 RBA=000004076C448594, checkpoint RBA=000004076C448594
 STC01435  CSQP021I +MQP4 Page set 3 new media recovery  789
 RBA=000004075921B0A0, checkpoint RBA=000004075921B0A0
 STC01435  CSQP021I +MQP4 Page set 4 new media recovery  790
 RBA=00000407583CF000, checkpoint RBA=00000407583CF000
 STC01435  CSQY220I +MQP4 CSQSCTL Queue manager storage usage:  597
 local storage: used 272MB, free 1203MB: above bar: used 230MB, free
 1GB
 STC01435  CSQJ110E +MQP4 LAST COPY 1 ACTIVE LOG DATA SET IS 5 PERCENT FULL
 STC01435  CSQJ110E +MQP4 LAST COPY 2 ACTIVE LOG DATA SET IS 5 PERCENT FULL
 STC01435  CSQJ110E +MQP4 LAST COPY 1 ACTIVE LOG DATA SET IS 10 PERCENT FULL
 STC01435  CSQJ110E +MQP4 LAST COPY 2 ACTIVE LOG DATA SET IS 10 PERCENT FULL
 |  |  
		  | Back to top |  |  
		  |  |  
		  | bruce2359 | 
			  
				|  Posted: Tue Dec 06, 2016 3:59 am    Post subject: |   |  |  
		  |  Poobah
 
 
 Joined: 05 Jan 2008Posts: 9486
 Location: US: west coast, almost. Otherwise, enroute.
 
 | 
			  
				| Have you opened a PMR with IBM on this issue?  It could be a bug in your new service level. 
 What else is new in that LPAR?  Any new applications?  Any recompiled applications?  Any applications that increased message size?
 
 It seems to me that one (or more) applications on the affected qmgr is MQPUTting more persistent messages (requiring log writes) in a given time period, and filling up your 4 log extents.  It looks like each of your 4 log segments is 15000 tracks - roughly 4GB each, for a total of 16GB of log space.
 
 A qmgr must have sufficient (number and size of) log extents to allow archives to complete before active logs become full.  This is a planning (or lack of) issue.
 
 "Number of" log extents is important because an active log cannot be archived if it contains an active Unit of Work.  It is possible for a long-running UofW to cause to have active log entries in all 4 of your log extents.  You will need to identify active applications running when this issue arises.  "Size of" messages is important because large messages will fill your logs quickly.  What are the message sizes on this qmgr?
 
 Find the person who decided on 4 log extents of 15000 tracks, and ask him/her how he/she determined that this was adequate?  I'll take a guess that this qmgr was clones from another existing qmgr, with no log calculation.  How to calculate log size is well-documented in the setup guide for IBM MQ on z/OS.
 _________________
 I like deadlines. I like to wave as they pass by.
 ב''ה
 Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
 |  |  
		  | Back to top |  |  
		  |  |  
		  | Vitor | 
			  
				|  Posted: Tue Dec 06, 2016 5:43 am    Post subject: |   |  |  
		  |  Grand High Poobah
 
 
 Joined: 11 Nov 2005Posts: 26093
 Location: Texas, USA
 
 | 
			  
				|   
 See my comments above.
 _________________
 Honesty is the best policy.
 Insanity is the best defence.
 |  |  
		  | Back to top |  |  
		  |  |  
		  |  |  |  
  
	|    |  | Page 1 of 1 |  
 
 
  
  	| 
		
		  | 
 
 | You cannot post new topics in this forum You cannot reply to topics in this forum
 You cannot edit your posts in this forum
 You cannot delete your posts in this forum
 You cannot vote in polls in this forum
 
 |  |  |  |