The CA Inter‑Product Components (CA IPCs) provide common functions to CA Ideal and an interface between CA Ideal and the external environment. These programs let CA Ideal process user requests and provide the services requested while remaining independent of the operating system and teleprocessing monitor.
Acts as a software interface between CA Ideal and the teleprocessing monitor, operating system, and database. All external services CA Ideal requires are invoked through VPE. Other CA IPCs also use VPE for their external services.
VPE handles requests for services such as memory management, program management, resource management, I/O services, enqueue and dequeue, dynamic batch job submission, and database accesses. It handles these requests for service through macro calls and performs the functions according to the rules and syntax of the host environment.
Processes the CA Ideal commands that define, paint, and test panels interactively.
Processes, routes, and manages print requests. PSS handles CA Ideal commands for maintaining the output library, browsing output, and performing other print services.
Set up run‑time services for acquiring, sending, receiving, and managing 327x‑type terminal messages. PMS validates date and time stamps and checks input fields for violations of panel edit rules. PMS supports both CA Ideal product panels and application panels developed using PDF.
Handle user requests from an online terminal session and a CA Ideal batch session. SCF provides CA Ideal sign‑on processing, handles asynchronous compiles and network printing, and processes commands such as DISPLAY ERROR; SPLIT and COMBINE; SCROLL; and HELP, RETURN, and CLARIFY.
SCF also acts as a command dispatcher, managing CA Ideal menus, commands, and PF and PA keys; separating commands; and passing commands to the appropriate CA Ideal module for further analysis. In batch, SCF prints commands as though they were entered in an online environment.
Uses the basic I/O services of VPE to store, retrieve, and modify data in both online and batch environments.
There are two types of VLS library members. Record members store source data in source libraries and output in the output library. Block data members store variable‑length data in panel libraries or object libraries.
A site can define additional source, object, and panel libraries.
VLS has a batch utility for library maintenance (VLSUTIL). For more information about its usage, see the Administration Guide.
Maps fill‑in panels to VLS members providing editing commands and checkpoint and rollback functions.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|