Digital SNA 3270 Application Services for Digital UNIX Version 1.2 Release Notes June 12, 1996 Copyright (c) 1996 Electronic Data Systems Corporation. All rights reserved. Copyright (c) 1992, 1994 by Digital Equipment Corporation. All rights reserved. This document contains information not included elsewhere in the Digital SNA 3270 Application Services for Digital UNIX V1.2 documentation. It includes information about software problems and documentation changes. IMPORTANT Please read these notes before installing or using the software. Revision Information: This is a new document. Operating System Version: Digital UNIX V3.2 Software Version: Digital SNA 3270 Application Services for Digital UNIX V1.2 Copyright (c) 1996 Electronic Data Systems Corporation Contents 1 INTRODUCTION 1 2 REQUIRED SOFTWARE 1 3 FEATURES NEW TO V1.2 1 3.1 TCP/IP or DECnet 1 3.2 Support for pthreads 1 3.3 Updated include files 1 3.4 License checking 2 4 ADDITIONAL DOCUMENTATION 2 4.1 Testing under Digital UNIX 2 5 KNOWN PROBLEMS AND PRODUCT RESTRICTIONS 2 5.1 Programming and Management manual available in hard copy only 2 5.2 Only R3270_C_BLOCKED callmode supported 3 5.3 r3270_cancel_receive not supported 3 5.4 Time out on r3270_connect not supported 3 5.5 Parameter checking 3 6 PROBLEMS FIXED IN V1.2 3 6.1 Infinite loop 3 6.2 Device hang when SNA_S_TOEXR returned 3 6.3 Sequence number >= 0x0100 problem 4 6.4 SEGV fault when REQUEST_TO_TRANSMIT is outstanding 4 6.5 Problem in r3270_example.c 4 6.6 PAI problem in SNALOG 4 6.7 PAI DFCI Fix internal -RSP completion processing 4 iii 1 Introduction These release notes are for the Digital SNA 3270 Application Services for Digital UNIX V1.2 for Digital UNIX. The abbre- viated name of this product is "3270 Services" and is used throughout this document. Following product installation this file can be found in /usr/sna/R3270_V12-0_release_notes. 2 Required Software The 3270 Services software requires Digital UNIX V3.2 or higher. 3 Features new to V1.2 3.1 TCP/IP or DECnet 3720 Services on Digital UNIX supports both TCP/IP and DECnet/OSI. TCP/IP is the default. To get DECnet/OSI (on a process-wide basis), define the envi- ronment variable R3270_TRANSPORT to be "decnet" before running the program which uses 3270 Services, ie: export R3270_TRANSPORT=decnet 3.2 Support for pthreads 3270 Services is completely pthread-safe. Calls to r3270_xxx verbs may be made simultaneously from multiple threads. 3.3 Updated include files The include files: /usr/include/r3270msg.h /usr/include/sna3270.h /usr/include/snamsg.h are no longer supplied. The contents of these files are now included in the include file: /usr/include/r3270def.h 1 3.4 License checking The following licenses are available for the product. These license are checked in the following order. If no license is installed, or an installed user license returns an error then the last license in this list is the one that is listed in the license error message. o SNA-3270-SVCS-DEV o SNA-3270-SVCS-RT o SNA-3270-SVCS-DEV-USER o SNA-3270-SVCS-RT-USER 4 Additional Documentation 4.1 Testing under Digital UNIX Refer to Chapter 5 of the Digital SNA 3270 Application Services Programming and Management for general information on test- ing your application. In addition to the testing procedures outlined there you may use the DECwindows SNA 3270 Terminal Emulator for Digital UNIX to test out your 3270 Services appli- cation. In order to use the 3270 Terminal Emulator you must set up your application to declare itself as DECnet object 10 or on TCP/IP port 108. You then use the terminal emulator to con- nect to the application under test as if it were a Digital SNA Gateway. Unlike with the OpenVMS 3270 terminal emulator there is no way to force the Digital UNIX 3270 terminal emulator to connect to anything other than DECnet object 10 or TCP/IP port 108. 5 Known Problems and Product Restrictions 5.1 Programming and Management manual available in hard copy only The Digital SNA 3270 Application Services Programming and Management manual is not available in Bookreader format on the Digital UNIX Consolidated On-Line Documentation CDROM. A hard copy of this manual can be obtained by ordering the full documentation set for the 3270 Services product (part number QA-MKJAA-GZ) or by ordering the manual individually (part num- ber AA-PPV3C-TK). The Digital SNA 3270 Services Installation manual is supplied in Bookreader format on the Digital UNIX Consolidated On-Line Documentation CDROM. 2 5.2 Only R3270_C_BLOCKED callmode supported All verbs only support the blocked callmode. Verbs issued with a callmode of R3270_C_CALLBACK are rejected with R3270_ S_INVCALLMODE. Any callback parameters specified with the verbs are ignored. 5.3 r3270_cancel_receive not supported The cancel receive verb (r3270_cancel_receive) is not supported for this release. 5.4 Time out on r3270_connect not supported The time-out parameter for the r3270_connect verb is not sup- ported. If specified it is ignored. 5.5 Parameter checking If a verb is called with an illegal parameter then a SEGV fault may occur. This is because parameters passed to the verbs are accessed without first checking that accessing them is possi- ble. 6 Problems Fixed in V1.2 3270 Services V1.2 includes the following fixes added since the V1.1 release of the 3270 Services product. 6.1 Infinite loop Fixed two infinite loop problems: o When writing from the pacing queue as the link was aborted. o When trying to remove the tc_to_dfcq to the user queue as 081B was received. 6.2 Device hang when SNA_S_TOEXR returned Fixed the R3270 device hang problem when the error status SNA_ S_TOEXR is returned. 3 6.3 Sequence number >= 0x0100 problem There was a bug extracting the sequence number from the receive buffer. The code was mistakenly taking the byte at the location in msg_ptr and extending it to an unsigned short int. What was really needed was to reference the unsigned short int starting at this location. Code was added to copy the 2 bytes needed for the sequence number into an unsigned short int local variable. 6.4 SEGV fault when REQUEST_TO_TRANSMIT is outstanding The SEGV occurred when the following were true: o R3270$REQUEST_TO_TRANSMIT is called. o At that very moment (ie. while REQUEST_TO_TRANSMIT is out- standing) the session to the IBM system is lost and the Gateway/IBM system sends an UNBIND RU. 6.5 Problem in r3270_example.c The internal error message R3270_S_BUGCHK is returned when r3270_connect fails. R3270_S_BUGCHK - a fatal error in R3270 has occurred R3270_S_BUGCHK - status = 55982ba Fixed by adding a call to r3270_deallocate_session call in order to deallocate memory if r3270_connect returns an error. 6.6 PAI problem in SNALOG Handle a status vector on non OpenVMS platforms in routine sna- log_status. 3270 Services on Digital UNIX uses status vectors and without this fix 0 is often erroneously logged as routine return values. 6.7 PAI DFCI Fix internal -RSP completion processing If a message was received that needed a response internally in a lower layer, the completion of the sending of the -RSP caused the outstanding R3270 receive to complete erroneously. 4