What are the main commands and their syntax?

The primary command is `PIESTEP`. It is used to define and manage the rules for STEPLIB and ISPLLIB concatenation. The syntax includes options for specifying application IDs, user IDs, and the libraries to be included in the concatenation. For example: `PIESTEP ADD APPID(APP123) LIB(SYS1.LINKLIB, USER.LOADLIB)`.

How is the product configured?

Configuration is managed through a dedicated ISPF panel interface. This interface allows administrators to define, modify, and delete rules. The rules are stored in a control file that is accessed by the PIE/TSO Dynamic Steplib component during ISPF application initialization.

What type of API is exposed?

The product uses a native API for integration with ISPF. This API intercepts the ISPF application initialization process. It then applies the defined rules to modify the STEPLIB and ISPLLIB concatenations. This ensures that the correct libraries are available for each application.

How does PIE/TSO Dynamic Steplib improve business value?

PIE/TSO Dynamic Steplib reduces the time system programmers spend on managing ISPF application environments. It automates the process of updating STEPLIB and ISPLLIB concatenations. This leads to increased productivity and reduced operational costs.

How does PIE/TSO Dynamic Steplib improve application stability?

By ensuring that the correct libraries are always available, PIE/TSO Dynamic Steplib reduces the risk of application failures. This leads to improved application stability and reduces the need for troubleshooting. It also minimizes downtime.

How does PIE/TSO Dynamic Steplib simplify ISPF application management?

The product simplifies the management of ISPF application environments. It reduces the complexity of maintaining these environments. This leads to fewer errors and improved application stability.

What authentication methods are supported?

PIE/TSO Dynamic Steplib does not directly provide authentication. Security is managed through z/OS security features. Access to the product's ISPF panels and control files should be secured using RACF or similar security products.

What access control model is used?

Access control is managed through z/OS security products such as RACF or ACF2. These products are used to control access to the ISPF panels and control files used by PIE/TSO Dynamic Steplib. This ensures that only authorized users can modify the configuration.

What encryption is used and where?

The product does not perform encryption. Security relies on the underlying z/OS security infrastructure. Sensitive data, such as library names and user IDs, should be protected through appropriate z/OS security measures.

What audit/logging capabilities exist?

Audit logging is provided through standard z/OS logging mechanisms. Security events, such as unauthorized access attempts, are logged by the z/OS security product (e.g., RACF). These logs can be used for security audits.

What administrative interfaces are available?

The primary administrative interface is an ISPF panel. This panel allows administrators to define and manage the rules for STEPLIB and ISPLLIB concatenation. It provides a user-friendly interface for configuring the product.

How is user management handled?

User management is handled through the z/OS security system (e.g., RACF). Access to the ISPF panels and control files is controlled by defining appropriate permissions in RACF. This ensures that only authorized users can modify the configuration.

What are the main configuration parameters?

The main configuration parameters include application IDs, user IDs, and the libraries to be included in the STEPLIB and ISPLLIB concatenations. These parameters are defined through the ISPF panel interface. They are stored in a control file.

What monitoring/logging capabilities exist?

Monitoring is performed through standard z/OS monitoring tools. The product does not have specific monitoring capabilities. System administrators can monitor the product's activity by reviewing the z/OS system logs and security logs.

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

PIE/TSO Dynamic Steplib

UNICOM Systems Active z/OS

Program and Load Libraries TSO/ISPF

Vendor

UNICOM Systems

Product Overview

The architecture of PIE/TSO Dynamic Steplib centers around the Dynamic Steplib Manager, a core component residing within the z/OS environment. This manager intercepts the ISPF application initialization process. It then applies predefined rules to modify the STEPLIB and ISPLLIB concatenations.

The ISPF panel interface provides the primary means of configuration and administration. The rules are stored in a control file. This file is accessed by the Dynamic Steplib Manager during application initialization.

The product integrates with ISPF through a native API, ensuring seamless operation. Security relies on the z/OS security infrastructure, such as RACF or ACF2, for access control. The communication flow involves the ISPF application, the Dynamic Steplib Manager, the control file, and the z/OS security system.

The product does not use any external databases or require specific network ports.

Frequently Asked Questions

What is the primary function of PIE/TSO Dynamic Steplib?

PIE/TSO Dynamic Steplib allows dynamic modification of the TSO STEPLIB and ISPLLIB concatenations for each ISPF application. This eliminates the need for system programmers to manually update these libraries. It enhances ISPF application management and reduces the risk of environment-related errors.

How does PIE/TSO Dynamic Steplib manage library concatenations?

Users can define rules to control library concatenations based on ISPF application IDs or user IDs. These rules are applied dynamically when an ISPF application is invoked. This ensures that the correct libraries are available for each application, improving reliability.

How does PIE/TSO Dynamic Steplib integrate with the z/OS environment?

The product integrates with ISPF and TSO environments. It intercepts ISPF application initialization and applies the defined rules to modify the STEPLIB and ISPLLIB. This integration is seamless, requiring no changes to existing ISPF applications.

What are the key benefits of using PIE/TSO Dynamic Steplib?

PIE/TSO Dynamic Steplib simplifies the management of ISPF application environments. It reduces the time and effort required to maintain these environments. This leads to fewer errors and improved application stability.

Related Products

Tape Tools and Utilities

View Details →