What infrastructure is required?

SYSJ requires a z/OS environment with CICS Transaction Server. It leverages JES2 for SYSOUT management. The specific version requirements depend on the SYSJ release.

For mainframe products: Does this run in an LPAR?

SYSJ runs within an LPAR on z/OS. It is dependent on the z/OS operating system and requires CICS Transaction Server to be present.

Does this extend/enhance another product?

SYSJ extends the capabilities of CICS by providing a way to create and manage JES2 SYSOUT datasets. It enhances CICS applications with output management features.

What other products or components must be present for this to work?

SYSJ relies on CICS for transaction processing and JES2 for output management. These components must be properly configured and running for SYSJ to function correctly.

What business problem does it solve?

SYSJ solves the business problem of integrating output management directly into CICS applications. Without it, organizations would need to develop custom solutions or rely on manual processes for generating reports and documents.

What would happen if an organization did NOT use this product?

If an organization did not use SYSJ, they would need to find alternative ways to generate reports, send notifications, or create documents from their CICS applications. This could involve custom programming, manual processes, or other third-party tools.

What is the business value of SYSJ?

SYSJ provides value by streamlining output management processes within CICS applications. This can lead to improved efficiency, reduced manual effort, and faster delivery of information to users.

How does SYSJ handle security?

SYSJ leverages the security features of z/OS and CICS to control access to SYSOUT datasets. It integrates with existing security systems to ensure that only authorized users can access sensitive information.

What authentication methods are supported?

SYSJ integrates with z/OS security systems, such as RACF, ACF2, or Top Secret, to authenticate users and control access to resources. It uses these systems to verify user identities and enforce access control policies.

What access control model is used?

SYSJ uses an access control model based on the underlying z/OS security system. This typically involves defining users and groups, assigning permissions to resources, and enforcing access control policies based on user roles or attributes.

How is SYSJ typically deployed?

SYSJ is typically deployed on-premise within a z/OS environment. It requires installation and configuration on the mainframe system.

What level of technical expertise is required to implement it?

Implementing SYSJ requires technical expertise in z/OS, CICS, and JES2. System programmers and CICS administrators are typically involved in the installation and configuration process.

What ongoing operational requirements exist?

Ongoing operational requirements for SYSJ include monitoring system performance, managing SYSOUT datasets, and ensuring the availability of CICS and JES2. Regular maintenance and updates may also be required.

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

SYSJ

H&W Computer Systems Supported z/OS

Printing and Output Application Development CICS

Vendor

H&W Computer Systems

Product Overview

SYSJ is an application development tool designed to allow CICS applications to create JES2 SYSOUT datasets. This enables functionalities such as sending emails or printing documents directly from within CICS. The architecture of SYSJ involves several key components working together to provide seamless integration with CICS and JES2.

The main components include the CICS interface module, the JES2 SYSOUT generation engine, and the security integration layer. The CICS interface module allows CICS applications to invoke SYSJ functions. The JES2 SYSOUT generation engine handles the creation and management of SYSOUT datasets.

The security integration layer ensures that access to SYSJ functions and data is controlled through z/OS security systems. SYSJ communicates with CICS using standard CICS programming interfaces and with JES2 using JES2 API. It integrates with z/OS security systems such as RACF, ACF2, or Top Secret for authentication and access control.

Alternatives include custom solutions or other CICS output management tools.

Frequently Asked Questions

What does SYSJ do?

SYSJ is an application development tool that allows CICS applications to create JES2 SYSOUT datasets. This enables functionalities such as sending emails or printing documents directly from within CICS.

Is this a system, application, or tool?

SYSJ is primarily an application development toolset. It provides the necessary components and interfaces to extend CICS applications with output management capabilities.

What types of organizations use this?

Organizations that rely on CICS for transaction processing and need to generate reports, send notifications, or create documents as part of their business processes would benefit from SYSJ. This includes businesses in finance, insurance, and retail.

When should we consider SYSJ?

A company should consider using SYSJ when they need to integrate output management capabilities directly into their CICS applications. This is especially useful when automating document generation, report distribution, or email notifications.

What are the alternatives to SYSJ?

Alternatives to SYSJ include other CICS output management solutions or developing custom solutions using CICS programming interfaces. However, SYSJ provides a pre-built and supported solution, potentially reducing development and maintenance efforts.

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

Share Your Product Experience

SYSJ

Product Overview

Frequently Asked Questions

What does SYSJ do?

Is this a system, application, or tool?

What types of organizations use this?

When should we consider SYSJ?

What are the alternatives to SYSJ?

What infrastructure is required?

For mainframe products: Does this run in an LPAR?

Does this extend/enhance another product?

What other products or components must be present for this to work?

What business problem does it solve?

What would happen if an organization did NOT use this product?

What is the business value of SYSJ?

How does SYSJ handle security?

What authentication methods are supported?

What access control model is used?

How is SYSJ typically deployed?

What level of technical expertise is required to implement it?

What ongoing operational requirements exist?

Related Products

More from H&W Computer Systems

CPMS

JES2Web

SYSB-II

SYSD

SYSM

WebTek

Similar Products

_beta doc|z plus

_beta doc|z transform

$avers

3270 SUPEROPTIMIZER/CICS

Ab Initio Business Rules Environment

Access Manager for CICS

Help Improve This Directory

Share Your Product Experience