U4038 - IGZ0099C Internal error CLOSE-FIB was detected in module IGZ@QSAM.
I have a program that abends with a U4038 on file close. This only happens when a specific record is on an input file. No record, no problem. This is from the dump - IGZ0099C Internal error CLOSE-FIB was detected in module IGZ@QSAM. From compile unit at entry point at compile unit offset +0B5A at entry offset +0B5A at address 7B5A. <> LEAID LEAID001I UNRECOGNIZED CEEMGET FEEDBACK CODE: x000301C259C3C5C50021 U4038 is usually associated with record or storage size. Is that correct? How can one record alter the size of a storage or record size? Regards, COG -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Interpreting SEND/RECV CIPHERs
Yes, AT-TLS is involved. This is an HTTPS call from Chrome to a port in a CICS region. The region is running Adaptigents Fabric (formerly Ivory). I've turned on the trace in ATTLS. I've also turned trace on for SYSLOGD and see that GSK_PROTOCOL_SSLV2, GSK_PROTOCOL_SSLV3 & GSK_PROTOCOL_TLSV1_2 are OFF. I'm currently waiting on Wireshare & getting STC id's for GSK trace. Is there any other way of seeing the protocol of the incoming HTTPS request? And for that matter, which protocol is used to receive the handshake? Thank you all, COG -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Interpreting SEND/RECV CIPHERs
>> 0090 EZD1285I TTLS Data CONNID: 0014 SEND CIPHER 1503020002020A >The 1503020002020A is an SSL alert packet with a fatal error: Unexpected >message This brief interchange comes from the archives. I need to find the meaning of a different cipher. I've gone through "IP Diagnosis" and didn't find any clues. Can anyone help? Thank you, COG -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: COBOL - z/OS 2.1 vs 2.4
I have further information from the programmers. These are CICS programs. The programs do not initialize their working storage. I'm told everything is fine under z/OS 2.1. Under z/OS 2.4, they are getting garbage in the COMMAREA. They want to know why it runs OK under 2.1. I have not found an answer for them in the migration guide. Can anyone help? COG -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
COBOL - z/OS 2.1 vs 2.4
We have a client with loadmods that are ancient. Some are very ancient. All of those loadmods are currently running under z/OS 2.1. Under z/OS 2.4, some of these loadmods are abending. Others are creating incorrect output. What could account for this behavior? What has changed between 2.1 & 2.4? Regards, Crusty Old Guy -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN