IBM 3.1 manual Improved performance and enterprise management, Threadsafe Web commands

Page 5

Code-page conversion enhancements The function to convert data between EBCDIC or ASCII and Unicode, in either direction, is now added to the existing CICS Transaction Server ASCIII and EBCDIC code-page conversions. This support uses IBM z/OS® conversion services.

The code-page conversion capability applies to either UTF-8 or UTF-16, and support is also provided for conversion between these forms of Unicode.

Improved performance and enterprise management

The enterprise-management focus in CICS Transaction Server, Version 3.1 has been on providing a simple, flexible, intuitive and comprehensive Web user interface (WUI) from which all the CICS regions and associated resources in the enterprise can be managed efficiently. IBM has enhanced support for the open

Enhanced open transaction environment CICS Transaction Server, Version 3.1 extends the use of the OTE by providing support for COBOL, PL/I, Assembler and non-XPLink C/C++ OPENAPI application programs. The program runs on its own task control block (TCB) from the start. OPENAPI requires the application to be coded to threadsafe standards. Using nonthreadsafe CICS commands can cause a switch to the quasi-reentrant TCB (QR TCB), so that CICS can switch back to the OTE TCB before returning control to the program.

The main benefit of this support is that it allows application workloads to be moved from a single QR TCB onto multiple TCBs, enabling better utilization of machine resources to achieve better throughput.

Threadsafe Web commands

All EXEC CICS Web API commands have been made threadsafe. These commands include WEB READ, WEB WRITE, WEB SEND, WEB RECEIVE, WEB RETRIEVE, WEB STARTBROWSE, WEB READNEXT, WEB ENDBROWSE, WEB EXTRACT, EXTRACT WEB, EXTRACT TCPIP and EXTRACT CERTIFICATE. This enhancement removes the requirement for CICS Transaction Server to return to the QR TCB to run these commands. As a result, applications (both Java and non-Java) that use these commands should be able to obtain the performance improvements resulting from reduced TCB switching. Also threadsafe are the new Web API commands that support outbound HTTP, such as WEB OPEN,

WEB CLOSE, WEB CONVERSE and WEB PARSE URL.

transaction environment (OTE) in CICS Transaction Server Version 3.1,

The program for this transaction is

The program for this transaction is

defined THREADSAFE, API= CICSAPI.

defined THREADSAFE, API= OPENAPI.

extended API threadsafety to include the EXEC CICS WEB API and improved the interface for C/C++ applications

QR TCB

Program start

EXEC CICS threadsafe

L8 TCB

QR TCB

L8 TCB

Program start

EXEC CICS threadsafe

to boost performance.

EXEC CICS nonthreadsafe

EXEC CICS nonthreadsafe

EXEC CICS nonthreadsafe

EXEC SQL

EXEC SQL

EXEC CICS threadsafe

EXEC SQL

EXEC SQL

EXEC RETURN

EXEC CICS nonthreadsafe

EXEC CICS nonthreadsafe

EXEC CICS nonthreadsafe

EXEC SQL

EXEC SQL

EXEC CICS threadsafe

EXEC SQL

EXEC SQL

EXEC RETURN

An OTE delivers improved transaction performance.

5

Image 5
Contents Highlights IBM Cics Transaction Server for z/OS, VersionEnhanced Http support Web services supportIncreased integration of Cics applications Application transformation Improvements to SSL supportLanguage Environment Main support for assembler Changed application using Program aImproved performance and enterprise management Threadsafe Web commandsCICSPlex System Manager WUI enhancements Enhanced C/C++ supportFunctionality immediately For more information Providing a common frameworkDesigned to meet your needs Hardware requirements IBM Cics Transaction Server, Version 3.1 at a glanceOther supported software

3.1 specifications

IBM 3.1 is known for its innovative approach to computing during an era that marked the transition into more advanced personal computing solutions. Launched as part of IBM's line of personal computers, IBM 3.1 was a notable product in the early 1990s, playing a crucial role in shaping the computing landscape.

One of the key features of IBM 3.1 was its use of the IBM PC DOS operating system, which provided a solid platform for business applications and productivity tools. The inclusion of a graphical user interface (GUI) improved usability compared to its predecessors, allowing users to navigate through tasks with ease.

The system architecture of IBM 3.1 was based on the Intel 80386 microprocessor, which was a leap forward in processing power and efficiency. It offered compatibility with earlier IBM PC models, making it easier for businesses to transition to newer technologies without losing investment in software and peripherals. The introduction of enhanced memory management capabilities allowed users to run multiple applications simultaneously, dramatically improving productivity.

IBM 3.1 also supported advanced technologies such as plug-and-play hardware components, which simplified system configuration and expanded upgrade potential. This feature allowed users to easily add peripherals like printers, modems, and external storage devices without the need for complex installations.

The integrated networking capabilities of IBM 3.1 enabled better connectivity between computers, fostering collaboration among users in office environments. Support for various networking protocols allowed seamless sharing of resources, which was essential in the growing landscape of networked computing.

In terms of storage, IBM 3.1 offered both hard drive options and upgraded floppy disk drives, catering to different user needs. The system supported a variety of software applications including word processors, spreadsheets, and database management systems, solidifying its place as a valuable tool for productivity.

Overall, IBM 3.1 was a groundbreaking personal computer that combined power, user-friendliness, and adaptability. It was a turning point in the evolution of IBM PCs, influencing the design and functionality of future computing products. With its forward-thinking technologies and robust feature set, IBM 3.1 left a lasting legacy in the world of personal computing.