Guides and samples which are not part of the formal product. If you need further information on any items here or would like to see something added please contact us by email at firstname.lastname@example.org.
- IPCS REXX execs for ALCS
- OCTM User Guide and Sample application
- System Takeover Facility
- High Load Monitor
- Allocatable Pool Presentation
- MQ Guide
- ALCS World Wide Web Server User Guide
- WTO Exit
- MQ Bridge Guide
- ALCS Performance Monitor
- VFA buffers above the 2GB bar
- Websphere Application Server optimized local adapter
- ALCS + Websphere Modernizing at High Speed brochure
- z/OS TCPIP Packet Trace
- ALCS online message trace
- AirAvailability Web service sample
To view system dumps the MVS tool used is IPCS, for which, REXX execs can format areas of storage. We have developed some IPCS REXX execs which may be used and we provide them here on an 'as is' basis. If you would like to try the execs then please download the files from the following links.
|ALCS 2.4.1||IPCS execs (ZIP, 30KB)||IPCS241 documentation (PDF, 47KB)|
The execs are not rigorous and may require tailoring for your installation.
OCTM is an ALCS system facility that provides an api (COMTC) through which an end user system can alter the communication definitions. Information on OCTM along with a description of a sample application are described in a manual available below.
|Sample application||EUSS applications (ZIP, 178KB)|
|Documents||OCTM User Guide (PDF, 323KB)|
ALCS has features that enable the setting up of an automated standby system. This guide discusses these features and how to exploit them.
When ALCS experiences a high work load, it is sometimes difficult to find out what the high load consists of.
The high load monitor is an update to ALCS monitor exit USRTIM2 to detect a high load situation and place information on the diagnostic file about each ECB in the system. An included offline program reads the diagnostic file and generates a simple report.
This presentation gives an overview of the concepts of allocatable pool. Why it is needed, how to migrate to it and how to expand pool once migration to Type 2 long term pool is complete.
This document describes the set up and use of Websphere MQ with ALCS. It is aimed at being a quick start guide for ALCS systems programmers and includes sample applications.
This book provides an introduction to the functions of the Airline Control System (ALCS) World Wide Web server (or just the ALCS Web server). It also explains how you use the ALCS Web server.
This package contains an example MVS Write to Operator exit. In this example the exit is used to invoke a CLIST when an ALCS realtime sequential file is deallocated. This could be developed to manage the archiving of these files to ensure that space is available for subsequent files.
This package contains an description of the ALCS MQ Bridge. The Bridge uses the MQ support in ALCS to provide connectivity to current ALCS applications from remote systems such as Web servers. It allows MQ messages received on request queues to be formatted and passed on to the applications as if they came from ordinary terminal devices.
The ALCS Performance Monitor satisfies User Group requirement ATC0262, which asked for the Performance Monitor developed by Jorge Widmar to be incorporated into ALCS. The documentation on the Performance monitor is in the standard manuals.
To assist those implementing the Performance Monitor for the first time we have collated the documentation from the standard manuals into a small document.
A guideline for migrating to an ALCS system with VFA buffers above the bar.
With WAS OLA support, you can create a web service to represent business logic implemented as a servlet or an Enterprise Java Bean (EJB). The application that gets control for the web service call can simply delegate to a connector call to ALCS. Using this approach, ALCS applications can readily be exposed externally as web services because all the necessary WAS external support and administration is in place.
When ALCS and WAS z/OS are co-located on the same LPAR, it opens up the possibility of using the WAS z/OS Optimized Local Adapters, or "OLA." OLA is a very fast cross-memory exchange mechanism. In this brochure we will spell out the value of that combination to you and your business.
A short guide for ALCS users on how to use the z/OS packet trace.
A guide to tracing input and output messages to a wrap around on-line trace area: msgtrace.pdf (PDF, 166KB).
A set of sample installation-wide exits msgtrace.zip (ZIP, 11KB).
This WebService sample demonstrates how an Open Travel Alliance (OTA) Air Availability Request (OTA_AirAvailRQ message) can be translated into an IBM ALCS (AirLine Control System) Air Availability Request, demonstrates how that translated request can be sent to a target ALCS system for processing, and how the ALCS Response can then be translated into an OTA Air Availability Response (OTA_AirAvailRS message) and returned to the caller.
For more information see "ALCS and WebSphere (PDF, 587KB)" in the Websphere Application Server optimized local adapter section (above).
See the ALCS WAS - OLA (PDF, 498KB) presentation from the 2011 Users Group meeting.
|Sample code:||ZIP (ZIP, 1.3MB)|
|Readme:||AirAvailability Readme text (TXT, 21KB)|
To view and print PDF files, you must have the Adobe Acrobat Reader software, which is available for free from the Adobe Web site: www.adobe.com/products/acrobat/readstep2.html.