Re: RE: IOSAS Abend 378-1C z/OS 1.13

"[email protected] [hercules-390]" <[email protected]>
Newsgroups gmane.comp.emulators.hercules390.general
Message-ID <[email protected]>
The following ZAP to SYS1.LINKLIB(IOSVCHPT) should do the trick...
 *
 * Prevent abend S378-1C in IOSAS during channel path table build.
 * The abend is caused by aliens pretending to support DCM,
 * which they in fact don't.
 *
  NAME IOSVCHPT
  IDRDATA ZAPALIEN
  VER 1F64 B218E000          PC   0(R14)       throws S378-1C when R1=0
  REP 1F64 A7F40196          BRC  15,ZAP378    branch into patch area
  VER 1F68 58B00010 RETRN378 L    R11,16(0,R0) return from patch area
  VER 2290 A292              DC   C'sk'        patch area pattern
  REP 2290 1211     ZAP378   LTR  R1,R1        R1=0?
  REP 2292 A784FE6B          BRC  8,RETRN378   yes, return to mainline
  REP 2296 B218E000          PC   0(R14)       no, release storage
  REP 229A A7F4FE67          BRC  15,RETRN378  return to mainline
 
---In [email protected], <werner02852@...> wrote :

 Hi,
 Has anyone found a solution on this issue ever ?
 I am using an IODF since many zOS releases without seeing this dump coming up. in z/OS2.3 i first see this dump. I have tried a lot with changing IODF but found no way to get this issue fixed in z/OS2.3.
 

 Please note: all is working fine, except this dump, which of course does not really hurt and can be supressed by a slip. Nevertheless it would be fine to find what is causing this issue coming up.
 

 I am using "latest" zOS2.3 service, so it`s no question of missing maintenance in operating system.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.