Carefully examine each fix for applicability before using it.

Fixes marked with "*" have been pre-applied to the currently available distribution file.

• Download Service Pack 1.5G (2012-03-05) with fixes pre-applied.

Download Fix File

When running multiple stacks and 15F is brought up before 15G external applications may fail because the system control block for 15F is smaller than 15G.

The 15G CSISTACK utility can be executed in the ASI ipl proc or before any stack is started to circumvent this problem. It will load a system control block that supports both 15F and 15G. But this is not required, and this zap should correct the problem.

Download Fix File

When issuing a SET HOST, or other variants, in order to connect to the SMTPD server, the DNS client will be invoked, but will be unable to resolve the IP address or domain name. This fix corrects that problem. You will also need to have applied ZP15G005 (IPNADNS update).

When "TEXT" was entered, all lines would be padded with X'00' which caused some attachment issued. This has been corrected.

When a "SET PDF=name" was entered, the attachment would appear to be a PDF, but it never ran through the PDF convertor. This has been corrected.

When the "SET FILETYPE=value" was entered, Email would try to execute a script called "name.L.value". This has been corrected.

You do not need to recycle the stack after applying this fix. ZP15G005 needs to also be applied. It will require recycling.

Download Fix File

Programs that run under the stack that call the API will hang because an special WAIT needs to be done. Setting "APIWAIT" to "I" for an INTERNAL wait, will correct this. For those programs that do not use IPNAPIB, they will not be affected by this fix.

To implement this correction, all API programs will need to be link-edited. This will only affect assembler programs that run under the TCP/IP stack.

ZP15G008 is a prerequisite. It provides the additional translation support needed by the API. Even if you do not use translation, this prerequisite is still needed.

Download Fix File

For those program that use IPNAPIB under that stack and also use the pre-processor, this will add some extra room to the control block to allow for some future definition expansion.

This will only affect assembler programs that run in the same partition as the TCP/IP stack.

Download Fix File

When SET MAILSERVER= is issued for Email, it tries to get an MX (Mail Exchange) record from the DNS server in order to determine the SMTPD address for that host. IPNADNS did not have this facility implemented.

IPNADNS now has this logic added. If a GetHostByName is requested with a "MX," prefix on the name, it will retrieve MX rather than A/AAAA records. This fix will require the recycling of the stack. Debugging information when doing this has also been corrected.

When the DNS client would "cache" the SMTD entry, it would use the domain name, causing problems when the domain name and the mail server are at different addresses. A "DNS Q" of the cache will now show an "MX," prefix on all resolved addresses done via MX records.

A "DNS Q" of the servers would show an incorrect average response time. This value has been corrected.

A recycling of the stack will be needed after applying this fix for it to take effect.

Download Fix File

If an external source deletes a report that is "in flight", AutoLPR will fail, but will keep trying until it runs out of RETRY count. This can cause a reduction in output speed for those sites that produce a lot of output.

CLIENTD will now check if a file is missing, and if so it will not perform a retry, but will just fail. A recycle of the stack is needed for this fix to go into effect.

Download Fix File

Because of changes to 15G, certain internal changes needed to be made to the client for it to be able to function. However, in doing so, some of the parameter logic no longer worked because of the new internal formatting structure.

This module replacement corrects those problems. You do not need to recycle the stack after applying this fix.

Download Fix File

This fix will permit the API to address all of the defined translation table details with a new internal command.

This fix requires that the stack is restarted after applying.

Download Fix File

As with IPNAPIB, this module was enhanced to support all existing SBCS translation under the initial 15G release.

To implement this correction, all API CICS programs will need to be link-edited and NEWCOPY'ed. ZP15G008 is a prerequisite.

Download Fix File

This fix will enable all known clients. This is a pre-req to using RSH, REXEC, WHOIS, and POPMAIL. See those related clients for their fixes as well.

After applying this fix, you will need to recycle the stack.

Download Fix File

Because of the changes to 15G, the client programs for RSH/REXEC needed to be modified in order to function.

If you use REXEC or RSH in your environment, then you should apply this fix. ZA15G010 will need to be applied for the internal client manager to find this update. No recycling of the stack is required after appling this fix (ZP15G010 will require a stack recycle).

Download Fix File

The logic for using the new extended parameters was in error. That has been fixed. ZP15G019 should also be applied with this one.

You should recycle your stack after applying this fix.

Download Fix File

Because of the changes to 15G, the client programs for WHOIS needed to be modified in order to function.

If you use WHOIS in your environment, then you should apply this fix. ZA15G010 will need to be applied for the internal client manager to find this update. No recycling of the stack is required after appling this fix (ZP15G010 will require a stack recycle).

It should also be noted that, over the past few years, many sites have closed off their WHOIS port (43) and have changed over to a web interface to provent abuse of this feature. If you find that your OPEN connection tines out, then it is likely because that hosting site has closed off that port and you will need to find a site that will permit the user of WHOIS from a remote user.

Download Fix File

Because of changes to 15G, certain internal changes needed to be made to the client for it to be able to function. This fix applies those changes to the internal client, IPNACMP3.

You do not need to recycle the stack after applying this fix.

Download Fix File

Because of changes to 15G, certain internal changes needed to be made to the client for it to be able to function. This fix applies those changes to the external client, POPMAIL.

You do not need to recycle the stack after applying this fix.

Download Fix File

When the external EMAIL client would read data from SYSIPT, it would send every card, including comments (those that have a "*" in column 1) to the internal Email client for processing. This would result in a cluttered SYSLST with the interspersed "Ready;" inserted after every comment, and added extra delays in processing.

You do not need to recycle the stack after applying this fix.

Download Fix File

The TCP/IP command reference documentation indicate that the DEFINE LINK with TYPE=LCS should be valid, but it is not recognized by the command parser. This zap corrects this problem.

The following deprecated SET commands are also no longer valid:

ADDITIONAL_WINDOW

REUSE_SIZE

Download Fix File

The TCP/IP command reference documentation indicate that the DEFINE LINK with TYPE=LCS should be valid, but it is not recognized by the command parser. This zap corrects this problem.

The following deprecated SET commands are also no longer valid:

ADDITIONAL_WINDOW

REUSE_SIZE

Download Fix File

When doing a lookup of an entry where a "not found" condition would be returned by the DNS server, a retry condition would occur by appending a suffix (if desired), but it would retry forever. That has been fixed.

Even though ZP15G012 had been applied to permit the changing of the TIMEOUT and APPEND and IPV6 parameters, the DNS client would not update that information in the DNS control block. That has been fixed.

When a DNS QUERY occurred, the average response time was always zero and the number of tries would be incorrect. That has been corrected.

If a DNS ADD SERVER follows a SET DNSx request, or visa-versa, and they have the same IP address, an informational message will tell you that a duplicate add was ignored. The table will no longer have a duplicate entry as a result.

For the DNS MODIFY correction to work, ZP15G012 needs to be applied as well. A recycling of the stack should be done after applying this fix.

Download Fix File

This zap provides a macro that can be used to create a phase containing the SHA-1 hash values for associated phases. This generated phase can then be used by the CIALSHPH utility to verify the integrity of phases in a library.

Download Fix File

This zap provides a new batch utility that can be used to verify a phase has a matching SHA-1 hash with jcl similar to this:

// EXEC CIALSHPH,SIZE=CIALSHPH

VERCHECK phasename

/*

Download Fix File

Various problems, such as an ABEND during initialization as well as a failure to connect while opening to the remote host were addressed.

This fix corrects those problems. No recycling of the stack is needed.

Download Fix File

The IBBLOK storage subpool is used for datagrams and the default amount of storage is the total amount of 24 and 31-bit getvis during the startup of TCP/IP. The QUERY IBBLOK can be used to determine the amount of storage currently allocated for IBBLOKs. This zap changes the maximum amount of storage to be the amount of free 31-bit partition getvis storage that will be used for IBBLOKs. The IBBLOK command can be used to set a new maximum amount of storage for IBBLOKs. The DIAG CLEANUP command can also be useful to monitor the getvis usage.

Download Fix File

This zap handles the failure of allocate storage for a IBBLOK for a OSAX link driver.

Download Fix File

Because of a bug with the GetHostByName call, any non-IP address (meaning, a domain name) would not be converted to the IP address, and the connection would fail. Also, the "// OPTION SYSPARM='nn'" value would not be used as the default SYSID, and if your stack was defined with a SYSID other than "00", it would fail. Finally, if you used "ID=nn", the GetHostByName would still use the default or SYSPARM value rather than the one used in "ID=".

This fix corrects those problems. No recycling of the stack is required. After applying, you will either need to NEWCOPY the CICS program "TELNET01", or recycle CICS for it to take effect.

Download Fix File

The socket allocation routine may abend when no storage is available. This zap corrects the problem by shutting down the CSOCKET subtask when no storage is available.

Download Fix File

When a SETHOST takes place, and a GetHostByName occurs, and a good IP address is returned, there are some situations where the request will do a false-failure and "HOST not found" would be displayed.

A long attach, such as "ATTACH POWER.LST.A.JOB" would fail, but a "CD POWER.LST.A" followed by "ATTACH JOB" would work. This was because of an imperfect directory positioning logic.

This fix corrects both of those problems.

There is no need to reinitialize the stack after applying this fix.

Download Fix File

If the stack would start the GPSD subtask before initializing the file directory structure, GPSD would fail to initialize and would display GPS904E "GPSD detected possible file system damage." Because of the multi-tasking engine, it is possible for GPSD to initialize before the file system, even if it appears directly after a DEFINE FILE in the initialization deck.

This fix causes GPSD to check for a file directory structure for up to a minute, and when it finds one, to continue normally. If, after a minute, it still cannot find one, it will fail as usual.

You should reinitialize your stack after applying this fix.

Download Fix File

Zapped phases were not being displayed in the Q VER output. This zap corrects this problem.

Download Fix File

Zapped phases were not being displayed in the Q VER output. This zap corrects this problem.

Download Fix File

The CICS client (CLIENT01) was using the old SOCKET CLIENT calls instead of the new SOCKET PROTO=CLIENT call. The result was that it was invoking the old 15F versions rather than the new 15G updated clients, and thus missing some of the features that had been added since 15G updates had been applied to those clients.

This fix changes CLIENT01 to use the new CLIENT calls and thus will use all of the 15G clients and all of the updates that had been applied to them.

There is no need to recycle the stack. You will need to NEWCOPY CLIENT01 under CICS for the new phase to take effect.

Download Fix File

Zapped phases were not being displayed in the Q VER output. This zap corrects this problem.

Download Fix File

Zapped phases were not being displayed in the Q VER output. This zap corrects this problem.

Download Fix File

Because the SET DISP= value was not being stored correctly, such setting as HOLD and DELETE would often fail.

This module replacement corrects those problems. You do not need to recycle the stack after applying this fix.

Download Fix File

A abend may occur with ZP15G023 applied. This zap corrects this problem.

Download Fix File

STRIPCC is supposed to srtip off the first byte of a line and reduce the line size by 1. Instead it includes the first byte and truncates the last byte of the line.

This fix corrects the problem. You will need to recycle the stack after applying this fix for it to take effect.

Download Fix File

When invoking a REXX CGI from HTTPD, because of a storage pointer problem, the FILE I/O subsystem would abend, causing the stack to no longer be usable.

This fix corrects the problem. You will need to recycle the stack after applying this fix for it to take effect.

Download Fix File

When an invalid parameter was entered in the execution parameter, CLIENT would Abend while trying to CLOSE a SOCKET that was never opened. Also, the "PRINT powrname/" format did not include the segment numbers when generating the "PRINT powrname" commands, causing the first segment to be sent repeatedly.

This module replacement corrects those problems. You do not need to recycle the stack after applying this fix.

Download Fix File

The logic for connecting to a host if an IP string was passed, rather than a name was in error, and so a connection would always fail. Also, the username was prefixed by 2 bytes of garbage. This has also been corrected so that the login does not fail due to a security mismatch. Finally, this client is fully IPv6 compliant.

If you use REXEC or RSH in your environment, then you should apply this fix. The stack should be recycled after applying.

Download Fix File

This Server handles REXEC and RSH services. Because RSH has one less parameter being passed to it, the list of variables that were set for the SHELL.PROC (REXX program) were off by one for RSH.

This fix corrects those problems for DEFINE SHELL. The stack should be recycled after applying.

Download Fix File

This fix corrects that problem. No recycling of the stack is needed after applying this fix.

Download Fix File

If a response greater than 8k bytes was returned from the WHOIS server, a bad calculation in the length would result in a translating of the response that was larger than the incoming data.

This fix corrects that problem. No recycling of the stack is needed after applying this fix.

Download Fix File

Because of an error in the GetHostByAddress logic, a SET HOST for FINGER would abend while trying to resolve the IP address.

This fix corrects that problem. No recycling of the stack is needed after applying this fix.

Download Fix File

When using client authentication a certificate is received and validated. But if the certificate_verify fails the client certificate is not returned to the application. This zap returns the client certificate even if the client certificate_verify fails.

The client cerificate information is returned in the SINIDATA-SIN@CINF field. The changes from ZP15F423 caused the two first fullwords or the returned client certificate information to contain binary zeros. They should contain the address and length of the client certificate in base64 format.

The verification of the client certificate_verify message is also corrected in this zap.

The returned serial number should be terminated with a null(x'00') but the workarea used was not being cleared and the serial number may not have been properly terminated with a null. This zap also corrects this problem.

This zap also includes the changes from ZP15F492 and ZP15F498.

This page and all materials residing on this site Copyright 1996, 2012 by CSI International. You may read, download, and copy these materials only for the purpose of evaluating or publicizing CSI International, its services and products or in accordance with a license agreement with CSI International.