Re: Network issue - device box status
You might need to set MIHPTO using the FICONCUPSET command. The default is 180 seconds and it can be set using a channel command, presumably you have connection software doing this to set it to 0. The specifics are hardware dependent, for example Brocade directors. Don't casually change the configuration if you aren't intimately familiar with these commands. On Sat, Jan 9, 2021 at 2:24 AM Prashant Joshi3 wrote: > Thanks Ken, > > I checked for default MIH values for these devices and they are set at 3 > minutes. However, once devices are allocated to Teradata, it gets changed > to 00 minutes. I am checking further. > Thanks a lot for these information. I think MIH definition will help. I > will let you know the results. > > Thanks, > Prashant > > > IBM Mainframe Discussion List wrote on > 08-01-2021 00:11:36: > > > From: Mazer Ken G <01e8b07bfbbe-dmarc-requ...@listserv.ua.edu> > > To: IBM-MAIN@LISTSERV.UA.EDU > > Date: 08-01-2021 00:12 > > Subject: [EXTERNAL] Re: Network issue - device box status > > Sent by: IBM Mainframe Discussion List > > > > Wow - I haven't heard Teradata in a number of years. Check to make > > sure your device addresses are still listed in IECIOSxx of SYS1.PARMLIB > > > > MIH DEV=(-),TIME=nn:nn > > > > Ken > > > > -Original Message- > > From: IBM Mainframe Discussion List On > > Behalf Of Prashant Joshi3 > > Sent: Thursday, January 07, 2021 1:18 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Network issue - device box status > > > > Hello, > > > > I have remote database (teradata) connected to mainframe using FICON > > channel (Type=dummy). Every time; there is a drop/glitch in network > > (microseconds) my mainframe devices get boxed and solution is to > > shutdown task, recycle devices, sometime it force to recycle chipids. > > Is there any way to increase network tolerance time to avoid device > > box status? > > > > > > Thanks, > > Prashant > > > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Network issue - device box status
Thanks Ken, I checked for default MIH values for these devices and they are set at 3 minutes. However, once devices are allocated to Teradata, it gets changed to 00 minutes. I am checking further. Thanks a lot for these information. I think MIH definition will help. I will let you know the results. Thanks, Prashant IBM Mainframe Discussion List wrote on 08-01-2021 00:11:36: > From: Mazer Ken G <01e8b07bfbbe-dmarc-requ...@listserv.ua.edu> > To: IBM-MAIN@LISTSERV.UA.EDU > Date: 08-01-2021 00:12 > Subject: [EXTERNAL] Re: Network issue - device box status > Sent by: IBM Mainframe Discussion List > > Wow - I haven't heard Teradata in a number of years. Check to make > sure your device addresses are still listed in IECIOSxx of SYS1.PARMLIB > > MIH DEV=(-),TIME=nn:nn > > Ken > > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Prashant Joshi3 > Sent: Thursday, January 07, 2021 1:18 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Network issue - device box status > > Hello, > > I have remote database (teradata) connected to mainframe using FICON > channel (Type=dummy). Every time; there is a drop/glitch in network > (microseconds) my mainframe devices get boxed and solution is to > shutdown task, recycle devices, sometime it force to recycle chipids. > Is there any way to increase network tolerance time to avoid device > box status? > > > Thanks, > Prashant > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Network issue - device box status
Wow - I haven't heard Teradata in a number of years. Check to make sure your device addresses are still listed in IECIOSxx of SYS1.PARMLIB MIH DEV=(-),TIME=nn:nn Ken -Original Message- From: IBM Mainframe Discussion List On Behalf Of Prashant Joshi3 Sent: Thursday, January 07, 2021 1:18 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Network issue - device box status Hello, I have remote database (teradata) connected to mainframe using FICON channel (Type=dummy). Every time; there is a drop/glitch in network (microseconds) my mainframe devices get boxed and solution is to shutdown task, recycle devices, sometime it force to recycle chipids. Is there any way to increase network tolerance time to avoid device box status? Thanks, Prashant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Network issue - device box status
Hello, I have remote database (teradata) connected to mainframe using FICON channel (Type=dummy). Every time; there is a drop/glitch in network (microseconds) my mainframe devices get boxed and solution is to shutdown task, recycle devices, sometime it force to recycle chipids. Is there any way to increase network tolerance time to avoid device box status? Thanks, Prashant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
