Question 1

What is PEngiONL?

Accepted Answer

PEngiONL is a CASE tool designed for generating CICS/COBOL applications. It streamlines the development process by generating pure COBOL source code from design specifications, reducing manual coding efforts and improving application quality.

Question 2

How does PEngiONL generate COBOL code?

Accepted Answer

PEngiONL generates COBOL source code based on defined specifications. Developers define application logic, data structures, and user interfaces within the tool. PEngiONL then automatically produces the corresponding COBOL code, ready for compilation and deployment on z/OS.

Question 3

What type of CICS applications can be developed using PEngiONL?

Accepted Answer

PEngiONL supports the development of CICS applications. It provides features and code generation capabilities specifically tailored for the CICS environment, enabling developers to build and maintain CICS-based systems more efficiently.

Question 4

What platform does PEngiONL support?

Accepted Answer

PEngiONL is designed to run on the z/OS platform. It leverages the capabilities of the mainframe environment for application development and deployment, ensuring compatibility and performance within the z/OS ecosystem.

Question 5

What are the most common commands and their syntax?

Accepted Answer

Common commands include: GENERATE (to create COBOL code), COMPILE (to compile generated code), BUILD (to create executable modules), and DEPLOY (to deploy applications to CICS). The syntax typically involves specifying input files, output directories, and various options for code generation and compilation.

Question 6

What configuration files or interfaces are used?

Accepted Answer

PEngiONL uses configuration files to store settings such as database connection details, code generation preferences, and deployment targets. These files are typically in a structured format (e.g., text-based configuration files) and are used to customize the behavior of the tool.

Question 7

What are the main system components?

Accepted Answer

PEngiONL's architecture includes components like the Specification Processor, Code Generator, and Deployment Manager. The Specification Processor parses input specifications, the Code Generator produces COBOL source, and the Deployment Manager handles application deployment to the CICS environment.

Question 8

How are the generated COBOL source files processed?

Accepted Answer

The Code Generator produces COBOL source code. The generated code can then be compiled using a COBOL compiler. The compiled code is linked to create executable modules. These modules are then deployed to the CICS environment for execution.

Question 9

What protocols and ports are used for communication?

Accepted Answer

PEngiONL uses standard mainframe protocols for communication, including TCP/IP for network interactions. Specific port requirements depend on the CICS configuration and the services being accessed. Database interactions typically use standard database protocols supported by the z/OS environment.

Question 10

What is the business value of using PEngiONL?

Accepted Answer

PEngiONL reduces manual coding, accelerates development cycles, and improves code quality. By automating code generation, it minimizes errors and ensures consistency, leading to faster time-to-market for CICS/COBOL applications.

Question 11

How does PEngiONL reduce development costs?

Accepted Answer

PEngiONL helps reduce development costs by automating repetitive tasks. It allows developers to focus on application logic rather than writing boilerplate code, leading to increased productivity and lower overall project costs.

Question 12

How does PEngiONL improve application maintainability?

Accepted Answer

By generating consistent and well-structured COBOL code, PEngiONL improves application maintainability. The generated code adheres to predefined standards, making it easier for developers to understand, modify, and maintain applications over time.

Question 13

How does PEngiONL accelerate application delivery?

Accepted Answer

PEngiONL facilitates faster application delivery by automating code generation. This automation reduces the time required for coding, testing, and deployment, enabling organizations to respond quickly to changing business needs.

Question 14

What authentication methods are supported?

Accepted Answer

PEngiONL supports authentication through integration with security systems on z/OS. It leverages existing security infrastructure, such as RACF or similar security managers, to authenticate users and control access to resources.

Question 15

What access control model is used?

Accepted Answer

Access control is managed through the z/OS security infrastructure. PEngiONL integrates with the security manager to enforce role-based access control (RBAC), allowing administrators to define roles and assign permissions to users based on their responsibilities.

Question 16

What encryption is used and where?

Accepted Answer

PEngiONL does not directly provide encryption. Security is managed through the underlying z/OS environment. Data encryption is handled by the z/OS security features and any encryption capabilities within the CICS environment.

Question 17

What audit/logging capabilities exist?

Accepted Answer

PEngiONL integrates with z/OS logging and auditing mechanisms. All actions performed within PEngiONL are logged, and audit trails are created to track user activities and system events. These logs can be used for security monitoring and compliance purposes.

Question 18

What administrative interfaces are available?

Accepted Answer

Administrative interfaces are typically provided through a combination of ISPF panels and batch jobs. ISPF panels are used for interactive configuration and management tasks, while batch jobs automate tasks such as code generation and deployment.

Question 19

How is user management handled?

Accepted Answer

User management is handled through the z/OS security system, such as RACF. Administrators define user profiles and assign appropriate permissions to control access to PEngiONL resources and functionality.

Question 20

What are the main configuration parameters?

Accepted Answer

Main configuration parameters include settings for database connections, code generation options, and deployment targets. These parameters are typically stored in configuration files and can be modified through ISPF panels or batch jobs.

Question 21

What monitoring/logging capabilities exist?

Accepted Answer

PEngiONL provides logging capabilities to monitor system activity and troubleshoot issues. Logs capture information about code generation, compilation, and deployment processes. These logs can be used for performance monitoring and problem diagnosis.

Share Your Product Experience

PEngiONL

Product Overview

Frequently Asked Questions

What is PEngiONL?

How does PEngiONL generate COBOL code?

What type of CICS applications can be developed using PEngiONL?

What platform does PEngiONL support?

What are the most common commands and their syntax?

What configuration files or interfaces are used?

What are the main system components?

How are the generated COBOL source files processed?

What protocols and ports are used for communication?

What is the business value of using PEngiONL?

How does PEngiONL reduce development costs?

How does PEngiONL improve application maintainability?

How does PEngiONL accelerate application delivery?

What authentication methods are supported?

What access control model is used?

What encryption is used and where?

What audit/logging capabilities exist?

What administrative interfaces are available?

How is user management handled?

What are the main configuration parameters?

What monitoring/logging capabilities exist?

Related Products

More from Foundation Software

PEngiBAT

PEngiCCL

PEngiEZT

Similar Products

3270 SUPEROPTIMIZER/CICS

Ab Initio Business Rules Environment

Access Manager for CICS

Access Manager for IMS

ACCOLADE

ACI Host Link

Help Improve This Directory

Are You a Vendor? Claim Your Listing