IBM Data and AI

Welcome to the IBM Data and AI Ideas Portal for Clients!

We welcome and appreciate your feedback on IBM Data and AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal. If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
Clients:
  • Our team welcomes any feedback and suggestions you have for improving our offerings / products! This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.

  • If you have not registered on this portal please click on the following link and register. To complete registration you will need to open the email you will receive from Aha to confirm your identity. http://ibm.biz/IBM-Data-and-AI-Portal-Register

Additional Information:
  • The shorter URL for this site is: https://ibm.biz/IBM-Data-and-AI-Ideas

  • To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

  • Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

Add additional retry logic when there is a tape volume that is unavailable

Add additional retry logic to better recover from an I/O error while reading a block

 from an IMS log when there is a tape volume that is unavailable during change stream

 connect processing.

 

  (1)SalesForce Case TS002782852 - DRISRP - Internal Error in module MSBCLRIR   

  (2)SalesForce Case TS002758971 - CECC0209E Source server received notification of change

                                     stream error

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Dec 17 2019
  • Future consideration
Who would benefit from this IDEA? Customers who use IMS Replication
How should it work?

In this instance the IMS Classic server queried the IMS RECON for the data set name it was looking for, and then the

Classic server used SVC 99 Dynamic Allocation services to allocate the IMS archive log data set

'IMSP.IMP3.SLDS.D19268.T0431164.V48'. There was an allocation error when looking for the data set, and the error was

because on an attempted data set name allocation the requested volume where the data set

'IMSP.IMP3.SLDS.D19268.T0431164.V48' resided was not available (e.g., unmounted volume). and that error was propagated

back to the Classic server as error message CECZ0938E and error message CECZ0309E.

 

Log reading reached EOF for DSN IMSP.IMP3.SLDS.D19268.T0421212.V49 at the ending IMS log sequence number of

"000000030D51361A". Classic will then attempt to locate the next cataloged IMS log by checking not only for the

timestamp but also the next IMS Log Sequence Number (LSN+1). The Log Sequence Number +1 is "000000030D51361B" in IMS log

data set IMSP.IMP3.SLDS.D19268.T0431164.V48.

 

DSN=IMSP.IMP3.SLDS.D19268.T0421212.V49                 UNIT=CART             

 START = 2019.268 11:21:21.230249       FIRST DS LSN= 000000030C61F47C        

 STOP = 2019.268 11:31:16.405321       LAST DS LSN= 000000030D51361A        

 FILE SEQ=0001  #VOLUMES=0001                                                 

 CHECKPOINT TYPES=80: SIMPLE=Y SNAPQ=N DUMPQ=N PURGE=N FREEZE=N                 

 

 DSN=IMSP.IMP3.SLDS.D19268.T0431164.V48                 UNIT=CART           <===Tape R72963 not available to     

 START = 2019.268 11:31:16.405321       FIRST DS LSN= 000000030D51361B       to Classic at DSN allocation  

 STOP = 2019.268 11:40:46.825604       LAST DS LSN= 000000030E43292F        

 FILE SEQ=0001  #VOLUMES=0001                                                 

 CHECKPOINT TYPES=80: SIMPLE=Y SNAPQ=N DUMPQ=N PURGE=N FREEZE=N                 

 

 VOLSER=R72963 STOPTIME = 2019.268 11:40:46.825604                            

   CKPTCT=1  CHKPT ID = 2019.268 11:29:33.037515                            

   LOCK SEQUENCE#= D6C6F6873C33                                              

 

 

The data set IMSP.IMP3.SLDS.D19268.T0431164.V48 was found in the RECON, but the attempt to allocate

the IMS log data set failed when the Classic server used SVC 99 Dynamic Allocation services to

allocate the IMS archive log data set 'IMSP.IMP3.SLDS.D19268.T0431164.V48'. There was an allocation

error when looking for the data set, and the error was because on an attempted data set name

allocation the requested volume where the data set 'IMSP.IMP3.SLDS.D19268.T0431164.V48' resided was

not available (e.g., unmounted volume).

 

 2019-09-25-07.33.31.732337 RC(08), SpcRC(01110003), Data(00000004,02200000)                                

  Node(201), Task(11262032)                                                                               

  COMM,CNTL, func handleNormalEOF, line 7330 in SYS19182.T121336.RA000.CACBLDC0.PH13029.H02(MSBCLRIR)     

  '(P1-7185514, IMP3) Log openBSAM_imslog error                    '                                    

  'DSN: IMSP.IMP3.SLDS.D19268.T0431164.V48          Class 4 Error = Environmental Error                                       

  'SpcRC: 00590021 Data(00000004,02200000)     <==== Reason Code 220 = Unavailable System Resource                         

                                                       Requested volume not available - (dsname allocation)

 MVS Programming: Authorized Assembler Services Guide

Idea Priority High
Priority Justification The availability of SLDS tapes are limited due to storage requirements, so retry logic is needed to prevent the subscriptions from erroring out.
Customer Name Anthem, Inc.
  • Attach files

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions