Enhanced interprogram data transfer If you want to exchange more than 32KB of data between programs, CICS Transaction Server now includes a new application programming interface (API), which introduces containers and channels. Containers are named blocks of data for passing information between programs. Any number of containers can be passed between programs.

Containers are grouped together in named channels. Channels can be used as a standard mechanism for exchanging data between programs. A channel can be passed on EXEC CICS LINK, START, XCTL and RETURN commands. Data can be exchanged between systems by either using multiregion option (MRO) or intersystem communication (ISC). Channels provide a more-flexible and a more-structured method of

Channels can be used by applications written in any of the programming languages supported by CICS Transaction Server, Version 3.1. Options on the container API commands are provided for data conversion, giving you a much-simpler mechanism than that employed with a COMMAREA. Also, in COMMAREAs, application data conversion is controlled by the system programmer. With channels, application-data conversion is controlled by the application programmer using simple API commands, minimizing the need to involve the system programmer.

Language Environment MAIN support for assembler

CICS Transaction Server now includes support to enable coding of completely Language Environment technology-

enabled application programs in assembler. A new translator option, LEASM, is provided, which causes Language Environment function to be used to set up the program’s envi- ronment. This option eases integration of these applications into Language Environment, so that Language Environment services can run more easily, and improves debugger support.

64-bit addressing toleration Although CICS Transaction Server, Version 3.1 does not support

the running of 64-bit applications, it now supports 64-bit code running as task-related user exits (TRUEs) in a CICS address space. Extensions are provided to CICS Transaction Server abend-capture mechanisms to allow the contents of full 64-bit, general- purpose registers to be reported.

passing data between program components. Variation in the size and number of containers can conveniently be accommodated to allow easier evolution of the interfaces between programs. The size of a container is one accommodation, limited only by the amount of storage available. There is no limit to the number of containers that can be added to a channel. This mechanism also removes the need for programs to know the exact size of the data returned. When containers go out of scope, they can be automatically destroyed, relieving you of storage- management concerns.

Existing application with COMMAREA

Program A

EXEC CICS LINK PROGRAM(‘PROGRAMB’)

Changed application using

Program A

EXEC CICS PUT CONTAINER(structure name) CHANNEL(channel-name)

FROM(structure)

EXEC CICS LINK PROGRAM(‘PROGRAMB’) CHANNEL(channel-name)

EXEC CICS GET CONTAINER(structure-name) INTO(structure)

Program B

EXEC CICS ADDRESS

Program B EXEC CICS GET CONTAINER(structure- name)INTO(structure)

EXEC CICS PUT CONTAINER(structure-name)

Restrictions on the amount of data that can be exchanged have been removed by using channels and containers.

4

Page 3 Page 5
Page 4
Image 4
IBM 3.1 manual Language Environment Main support for assembler, Changed application using Program a
Page 3 Page 5

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.
Top Page Image Contents