Tuesday, June 1, 2010

Free Mainframe Ebook

This mainframe site aims to provide free ebook on mainframe, ibm mainframe, tso mainframe, cics mainframe, mainframe ftp, os 390, jcl mainframes, db2 mainframe, cobol mainframe, sas mainframe, mainframe computer, mainframe linux, mainframe database, zos mainframe, mainframe commands, mainframe rexx, mainframe programming, mainframe migration, mainframe server, mainframe applications, mainframe basics,z os, cics, ispf mainframe, mainframe racf, etc

Linux on the Mainframe

By John Eilert, Maria Eisenhaendler, Dorothea Matthaeus, Ingolf Salm
Linux on the Mainframe is the comprehensive guide to the fastest growing trend in IT. IBM's Linux experts present peerless instruction in the art of planning for and making the most of a Linux mainframe. This book's in-depth coverage includes virtualization, deployment, data management, debugging, security, systems management, application porting, and much more.
  • Sample companies that demonstrate the strengths and potential shortcomings of Linux on the mainframe
  • Complete business analysis, including Total Cost of Ownership, server consolidation techniques, and IT infrastructure simplification
  • Examples of deploying middleware and other tools
  • In-depth introductions to the latest trends, developments, and technologies related to Linux on the mainframe
  • Background information on mainframes and Linux for the lay reader
  • Key techniques for deploying Linux servers and building integrated server environments

For anyone involved in the planning, deploying, management, or administration of a mainframe, Linux on the Mainframe is a vital resource.

Click to Download
Labels:
Reactions:

The Value of the IBM System z and z/OS in Service-Oriented Architecture

Without doubt, Service-Oriented Architecture (SOA) is one of the most important topics on the agenda of any IT person. SOA involves a new vision of how to design, develop, and manage applications, but also puts new requirements on the underlying infrastructure.
This Redpaper redbook describes the infrastructure challenges that SOA brings to the table and how the IBM System z platform and the z/OS operating system address those challenges. An effective SOA implementation requires very high Quality of Services (QoS) from the underlying environment, and users demand security, availability, and simplified management of the services. These are fundamental characteristics of System z and z/OS, making them an ideal platform on which to design an SOA.
This paper presents an overview of SOA, describes the SOA reference architecture, and demonstrates how IBM System z and z/OS support the SOA requirements. Finally, it suggests an approach for SOA-enabling existing applications and provides several integration scenarios.
Labels:
Reactions:

RISC/6000 to Mainframe Using S/370 Channel Connections

This document provides examples connecting RS/6000 systems to VM and MVSsystems via Block Multiplexer and Enterprise Systems Connection channels.Examples are given using TCP/IP, SNA, and CLIO/S.
This document was written for customers and system engineers who plan toconnect RS/6000 systems to Mainframes using channel architectures. Someknowledge of AIX, VM, and MVS is assumed.
AIX Version 3.2.5 was used during the creation of this manual. Thereare some references to AIX Version 4. These are instances when adifference was known.
Labels:
Reactions:

IBM Tivoli Monitoring for Network Performance V2.1 The Mainframe Network Management Solution

This redbook explains the new IBM Tivoli Monitoring for Network Performance Version 2.1. This version of IBM Tivoli Monitoring for Network Performance provides a complete redesign of the z/OS TCP/IP management tools that is started by the NetView Performance Monitor for TCP/IP.
IBM Tivoli Monitoring for Network Performance provides a comprehensive TCP/IP stack monitoring for z/OS. It collects performance metrics from the z/OS Communication Servers system management interface, measuring response time and Simple Network Management Protocol (SNMP) Management Information Base (MIB) variable collection.
IBM Tivoli Monitoring for Network Performance uses strategic IBM software platforms such as WebSphere Application Server as the Web application platform and DB2 Universal Database as the central repository.
This redbook starts with exploring on the architecture of IBM Tivoli Monitoring for Network Performance and its components. We also discuss various implementation scenario and evaluate the benefits and drawbacks of each scenario. Implementation planning and consideration is presented and lastly operational consideration is explained.
Labels:
Reactions:

End-to-End Scheduling with OPC and TWS Mainframe and Distributed Environments

Tivoli OPC and Tivoli Workload Scheduler (formerly Maestro) are the two scheduling engines that make up Tivoli's integrated solution for enterprise scheduling. Tivoli OPC has a firm share of the mainframe scheduling market, and TWS is the scheduler of choice for distributed environments. Tivoli has now made available the Job Scheduling Console, addressing the end-to-end scheduling requirements that are central to multi-platform environments. Tivoli OPC 2.3 and Tivoli Workload Scheduler 7.0 can now be managed from this common graphical user interface, creating a best-of-breed cross-platform scheduling solution.
This IBM Redbook provides step-by-step setup instructions, as well as detailed troubleshooting guidelines for implementing OPC, TWS, and the Job Scheduling Console. It covers the most important features of both engines and provides illustrative practical usage scenarios, including exploitation of the new common GUI, installation and usage of Extended Agents, and advice on implementing high-availability environments. Users migrating from previous releases will find the migration checklists and the terminology translation tables extremely valuable.
This book is based on OPC 2.3 and TWS 7.0 and will be usefulto those customers who are working to integrate OPC and TWS, as well as those working with OPC or TWS alone.
Labels:
Reactions:

Introduction to the New Mainframe: Networking

This IBM Redbook is designed for a one-semester course intended to provide information systems students with the background knowledge and skills necessary to begin using the basic communications facilities of a mainframe-based system. It provides a broad understanding of networking principles and the hardware and software components necessary to allow the mainframe to participate in a high volume data communications network. It is part of a planned series of textbooks designed to introduce students to mainframe concepts and help prepare them for a career in large systems computing.
While many of the networking concepts covered are operating system-independent, the main emphasis is on the z/OS operating system. You are assumed to have successfully completed introductory courses in computer system concepts, including courses in computer organization and architecture, operating systems, data management and data communications, and systems design and analysis.
A basic understanding of z/OS job control, library structure, and system libraries is assumed. It is strongly recommended that you have already completed an introductory course on z/OS, such as one that uses Introduction to the New Mainframe: z/OS Basics or a comparable text. In some instances, the z/OS Basics course and the course associated with this textbook could be taken together.
Labels:
Reactions:

Introduction to the New Mainframe: z/OS Basics

This IBM Redbook provides students of information systems technology with the background knowledge and skills necessary to begin using the basic facilities of a mainframe computer. It is the first in a planned series of textbooks designed to introduce students to mainframe concepts and help prepare them for a career in large systems computing.
For optimal learning, students are assumed to have successfully completed an introductory course in computer system concepts, such as computer organization and architecture, operating systems, data management, or data communications. They should also have successfully completed courses in one or more programming languages, and be PC literate.
This textbook can also be used as a prerequisite for courses in advanced topics or for internships and special studies. It is not intended to be a complete text covering all aspects of mainframe operation, nor is it a reference book that discusses every feature and option of the mainframe facilities.
Others who will benefit from this course include experienced data processing professionals who have worked with non-mainframe platforms, or who are familiar with some aspects of the mainframe but want to become knowledgeable with other facilities and benefits of the mainframe environment.
As we go through this course, we suggest that the instructor alternate between text, lecture, discussions, and hands-on exercises. Many of the exercises are cumulative, and are designed to show the student how to design and implement the topic presented. The instructor-led discussions and hands-on exercises are an integral part of the course material, and can include topics not covered in this textbook.
This book is also offered with a textbook cover instead of a redbook cover in PDF and hardcopy formats.
Labels:
Reactions:

ORBIX E2A - COBOL Programmer’s Guide and Reference

Orbix E2A is a full implementation from IONA Technologies of the Common Object Request Broker Architecture (CORBA), as specified by the Object Management Group (OMG). Orbix E2A complies with the following specifications:
  • CORBA 2.3
  • GIOP 1.2 (default), 1.1, and 1.0

The Orbix E2A Application Server Platform Mainframe Edition is IONA.s implementation of the CORBA standard for the OS/390 platform. Orbix E2A Application Server Platform Mainframe Edition documentation is periodically updated. New versions between release are available at http://www.iona.com/docs.

If you need help with this or any other IONA products, contact IONA at support@iona.com. Comments on IONA documentation can be sent to doc-feedback@iona.com.

This guide is intended for COBOL application programmers who want to develop Orbix E2A applications in a native OS/390 environment.

The supported compilers are:

  • IBM COBOL for OS/390 & VM version 2.1.1.
  • IBM COBOL for OS/390 & VM version 2.1.2.
  • IBM COBOL for OS/390 & VM version 2.2.1.

The related documentation provided includes:

  • The PL/I Programmer.s Guide and Reference, which provides details bout developing, in a native OS/390 environment, Orbix E2A PL/I pplications that can run in batch, CICS, or IMS.
  • The CORBA Programmer.s Guide, C++ and the CORBA Programmers. Reference, C++, which provide details about developing Orbix E2A applications in C++ in various environments, including OS/390.
  • The Mainframe Migration Guide, which provides details of migration issues for users who have migrated from IONA.s Orbix 2.3-based solution for OS/390 to Orbix E2A Application Server Platform Mainframe Edition.
Click to Download
Labels:
Reactions:

IMS V9 Appl. Programming: Design Guide

This book is a guide for designing application programs for IMS(TM). It tells application programmers how to identify application data and analyze requirements for application processing. This book describes other tasks such as gathering requirements for database and message processing options and testing an application program.
This information is available as part of the DB2 Information Management Software Information Center for z/OS Solutions.
To view the information within the DB2 Information Management Software Information Center for z/OS Solutions, go to http://publib.boulder.ibm.com/infocenter/dzichelp. This information is also available in PDF and BookManager® formats. To get the most current versions of the PDF and BookManager formats, go to the IMS Library page at www.ibm.com/software/data/ims/library.html.
Labels:
Reactions:

CICS/ESA 3.3 Application Programming Guide

This book gives guidance in the use of the CICS/ESA application programming interface; it complements the reference information in the CICS/ESA Application Programming Reference.
This book gives guidance on writing CICS application programs in COBOL, C/370, PL/I, and assembler, to run under the IBM licensed program CICS/ESA (5665-403). (CICS is the IBM Customer Information Control System/Enterprise Systems Architecture.)
Reference information is in the CICS/ESA Application Programming Reference. For information on debugging CICS applications, see the CICS/ESA Problem Determination Guide.
This book is mainly for experienced application programmers who are relatively new to CICS. If you're a system programmer or system analyst, you should still find it useful.
You must be able to program in VS COBOL II, OS/VS COBOL, C/370, PL/I, or assembler.
Labels:
Reactions:

CICS/ESA 3.3 Application Programming Reference

What this book is about
This book describes the CICS/ESA application programming interface; it contains reference information needed to prepare COBOL, C/370, PL/I, and assembler-language application programs, using CICS commands, to be executed under CICS. Guidance information is in the CICS/ESA Application Programming Guide. For guidance information about debugging CICS applications, see the CICS/ESA Problem Determination Guide.
If you need to know more about where programming interface information is described, or about the definitions of the different types of information in the CICS library, you should read the CICS Library Guide.
Who this book is for
The book is intended primarily for use by application programmers, but will also be useful to system programmers and systems analysts.
What you need to know to understand this book
We assume that you have some experience in writing programs in COBOL, C/370, PL/I, or assembler language.
You should also have a knowledge of the CICS concepts and terminology introduced in the CICS/ESA Facilities and Planning Guide and you should have read the CICS Application Programming Primer (VS COBOL II) and the CICS/ESA Application Programming Guide.
How to use this book
This book is for reference. Each of the commands has a standard format, as follows:
  • The syntax of the command
  • A description of what the command does
  • An alphabetical list of the options and their functions
  • An alphabetical list of conditions, and their causes, that can occur during execution of a command.

Notes on terminology

  • VTAM refers to ACF/VTAM and to the record interface of ACF/TCAM.
  • ASM is used sometimes as the abbreviation for assembler language.

Click to Read More/Download

Labels:
Reactions:

Enterprise PL/I Programming Guide

This book is for PL/I programmers and system programmers. It helps you understand how to use Enterprise PL/I for z/OS in order to compile PL/I programs. It also describes the operating system features that you might need to optimize program performance or handle errors.
Important: Enterprise PL/I for z/OS will be referred to as Enterprise PL/I throughout this book.
Run-time environment for Enterprise PL/I for z/OS
Enterprise PL/I uses Language Environment® as its run-time environment. It conforms to Language Environment architecture and can share the run-time environment with other Language Environment-conforming languages.
Language Environment provides a common set of run-time options and callable services. It also improves interlanguage communication (ILC) between high-level languages (HLL) and assembler by eliminating language-specific initialization and termination on each ILC invocation.
Labels:
Reactions:

Enterprise PL/I Language Reference

This book is a reference for the programmer using the IBM PL/I compiler. It is not a tutorial, but is designed for the reader who already has a knowledge of the PL/I language and who requires reference information needed to write a program for an IBM PL/I compiler. It contains guidance information and general-use programming interfaces.
Because this book is a reference manual, it is not intended to be read from front to back, and terms can be used before they are defined. Terms are highlighted where they are defined in the book, and definitions are found in the glossary.

Improved performance

  • The compiler now handles even more conversions by generating inline code which means these conversions will be done much faster than previously. Also, all conversions done by library call are now flagged by the compiler.
  • The compiler-generated code now uses, in various situations, less stack storage.
  • The compiler now generates much better code for references to the TRANSLATE built-in function.
  • The compiler-generated code for SUBSCRIPTRANGE checking is now, for arrays with known bounds, twice as fast as before.
  • The ARCH and TUNE options now support 4 as a suboption, thereby allowing exploitation of instructions new to the zSeries machines.
  • ARCH(2), FLOAT(AFP) and TUNE(3) are now the default.

Click to Read More/Download

Labels:
Reactions:

z/OS V1R6.0 TSO/E REXX Reference

This document supports z/OS (5694-A01) and z/OS.e (5655-G52).
This document describes the z/OS TSO/E REXX Interpreter (hereafter referred to as the interpreter or language processor) and the REstructured eXtended eXecutor (called REXX) language. Together, the language processor and the REXX language are known as TSO/E REXX. This document is intended for experienced programmers, particularly those who have used a block-structured, high-level language (for example, PL/I, Algol, or Pascal).
TSO/E REXX is the implementation of SAA REXX on the MVS system. Although TSO/E provides support for REXX, you can run REXX programs (called REXX execs) in any MVS address space. That is, you can run a REXX exec in TSO/E and non-TSO/E address spaces.
Descriptions include the use and syntax of the language and explain how the language processor "interprets" the language as a program is running. The document also describes TSO/E external functions and REXX commands you can use in a REXX exec, programming services that let you interface with REXX and the language processor, and customizing services that let you customize REXX processing and how the language processor accesses and uses system services, such as storage and I/O requests.
Labels:
Reactions:

z/OS V1R6.0 DFSORT Application Programming Guide

This document is intended to help you to sort, merge, and copy data sets using DFSORT(TM). This document is not designed to teach you how to use DFSORT, but is for programmers who already have a basic understanding of DFSORT, and need a task-oriented guide and reference to its functions and options. If you are a new user, then you should read z/OS DFSORT: Getting Started first. z/OS DFSORT: Getting Started is a self-study guide that tells you what you need to know to begin using DFSORT quickly, with step-by-step examples and illustrations.
The various sections of this document present related information grouped according to tasks you want to do. The first three chapters of the document explain what you need to know to invoke and use DFSORT's primary record-processing functions. The remaining chapters explain more specialized features. The appendixes provide specific information about various topics.
"Introducing DFSORT" in topic 1.0, presents an overview of DFSORT, explaining what you can do with DFSORT and how you invoke DFSORT processing. It describes how DFSORT works, discusses data set formats and limitations, and explains the defaults that might have been modified during installation at your site.
"Invoking DFSORT with Job Control Language" in topic 2.0, explains how to use job control language (JCL) to run your DFSORT jobs. It explains how to code JOB, EXEC, and DD statements, and how you can use cataloged procedures and EXEC PARM options to simplify your JCL and override DFSORT defaults set during installation.
"Using DFSORT Program Control Statements" in topic 3.0, presents the DFSORT control statements you use to sort, merge, and copy data. It explains how to filter your data so you work only with the records you need, how to edit data by reformatting and summing records, and how to produce multiple output data sets and reports. It explains how to write statements that direct DFSORT to use your own routines during processing.
"Using Your Own User Exit Routines" in topic 4.0, describes how to use DFSORT's program exits to call your own routines during program processing. You can write routines to delete, insert, alter, and summarize records, and you can incorporate your own error-recovery routines.
"Invoking DFSORT from a Program" in topic 5.0, describes how you use a system macro instruction to initiate DFSORT processing from your own assembler program. It also lists specific restrictions on invoking DFSORT from PL/I and COBOL.
"Using ICETOOL" in topic 6.0, describes how to use the multi-purpose DFSORT utility ICETOOL. It explains the JCL and operators you can use to perform a variety of tasks with ICETOOL.
"Using Symbols for Fields and Constants" in topic 7.0, explains how to define symbols and use them in DFSORT control statements and ICETOOL operators.
"Using Extended Function Support" in topic 8.0, explains how to use the Extended Function Support (EFS) interface to tailor control statements, to handle user-defined data types and collating sequences, and to have DFSORT issue customized informational messages during processing.
"Improving Efficiency" in topic 9.0, recommends ways with which you can maximize DFSORT processing efficiency. This chapter covers a wide spectrum of improvements you can make, from designing individual applications for efficient processing at your site to using DFSORT features such as Hipersorting, dataspace sorting, and ICEGENER.
"Examples of DFSORT Job Streams" in topic 10.0, contains annotated example job streams for sorting, merging, and copying records.
Appendix A, "Using Work Space" in topic A.0, explains main storage considerations and how to estimate the amount of intermediate storage you might require when sorting data.
Appendix B, "Specification/Override of DFSORT Options" in topic B.0, contains a series of tables you can use to find the order of override for similar options that are specified in different sources.
Appendix C, "Data Format Descriptions" in topic C.0, gives examples of the assembled data formats.
Appendix D, "EBCDIC and ISCII/ASCII Collating Sequences" in topic D.0, lists the collating sequences from low to high order for EBCDIC and ISCII/ASCII characters.
Appendix E, "DFSORT Abend Processing" in topic E.0, describes the ESTAE recovery routine for processing abends, and the Checkpoint/Restart facility.
"Notices" in topic BACK_1, includes the notices, Programming Interface information, and the trademark list.
Labels:
Reactions:

z/OS V1R6.0 DFSORT: Getting Started

z/OS DFSORT: Getting Started is a user's guide and tutorial for DFSORT(TM) (Data Facility Sort). You should read it if you are new to z/OS V1R5, and need to learn the many ways you can use DFSORT and DFSORT's ICETOOL utility to process data sets. Both new and experienced DFSORT users can use this document as a general guide to the many features available with DFSORT and ICETOOL. This document introduces you to the JCL, control statements and features of DFSORT and ICETOOL with numerous examples. z/OS DFSORT: Getting Started can help you get the most out of z/OS DFSORT Application Programming Guide, which has the complete details on all of the topics introduced in this document.
The chapters in this document assume that you have used job control language (JCL) and understand how to work with data sets. You should also know what data sets are available at your site.
Labels:
Reactions:

OS/390 V2R10.0 MVS JCL User's Guide

This book describes the job control tasks needed to enter jobs into the operating system, control the system's processing of jobs, and request the resources needed to run jobs. To perform the tasks, programmers code job control statements. This book describes how to use these statements, which consist of:
  • Job control language (JCL) statements
  • Job entry subsystem 2 (JES2) control statements
  • Job entry subsystem 3 (JES3) control statements

This book is designed as a user's guide, to be used when deciding how to perform job control tasks. It does not describe how to code the statements. For an introduction to the statements and for coding information, see the companion book, OS/390 MVS JCL Reference, GC28-1757.

Introduction
For your program to execute on the computer and perform the work you designed it to do, your program must be processed by your operating system. Your operating system consists of a base control program (BCP) with a job entry subsystem (JES2 or JES3) and DFSMSdfp installed with it.

For the operating system to process a program, programmers must perform certain job control tasks. These tasks are performed through the job control statements, which are listed in the first chapter. The job control tasks are introduced in the second chapter as well as introductory information about JCL. The charts in the third chapter divide these tasks into detailed subtasks.

The tasks are:

  • Entering jobs
  • Processing jobs
  • Requesting resources

Click to Read More/Download

Labels:
Reactions:

OS/390 V2R10.0 MVS JCL Reference

This book describes the job control tasks needed to enter jobs into the OS/390 operating system, control the system's processing of jobs, and request the resources needed to run jobs. The book also contains a chapter that describes "started tasks" and how to set them up. To perform job control or started tasks, programmers code "job control statements." This book describes how to code these statements, which include:
  • Job control language (JCL) statements
  • Job entry control language (JECL) statements, which encompass:
    • Job entry subsystem 2 (JES2) control statements
    • Job entry subsystem 3 (JES3) control statements

This book is designed as a reference book, to be used while coding the statements. It contains some introductory material. Full explanations of the job control tasks are presented in a companion book, OS/390 MVS JCL User's Guide, GC28-1758.

This book is needed by system and application programmers who enter programs into the operating system. Those using this book should understand the concepts of job management and data management.

Click to Read More/Download

Labels:
Reactions:

MVS/ESA SP V5 JCL User's Guide

Introduction
For your program to execute on the computer and perform the work you designed it to do, your program must be processed by your operating system. Your operating system consists of a base control program (BCP) with a job entry subsystem (JES2 or JES3) and MVS/DFP installed with it.
For the operating system to process a program, programmers must perform certain job control tasks. These tasks are performed through the job control statements, which are listed in the first chapter. The job control tasks are introduced in the second chapter as well as introductory information about JCL. The charts in the third chapter divide these tasks into detailed subtasks.
The tasks are:
  • Entering jobs
  • Processing jobs
  • Requesting resources

Click to Read More/Download

Labels:
Reactions:

MVS/ESA SP V5 JCL Reference

This book lists the job control tasks needed to enter jobs into the operating system, control the system's processing of jobs, and request the resources needed to run jobs. This book also contains a chapter that describes started tasks and how to set them up. To perform these tasks, programmers code job control statements. This book describes how to code these statements, which consist of:
  • Job control language (JCL) statements
  • Job entry subsystem 2 (JES2) control statements
  • Job entry subsystem 3 (JES3) control statements.

This book is needed by system and application programmers who enter programs into the operating system. Those using this book should understand the concepts of job management and data management.

Click to Read More/Download

Labels:
Reactions:

Enterprise COBOL Programming Guide

Welcome to IBM Enterprise COBOL for z/OS, IBM's latest host COBOL compiler!
This version of IBM COBOL adds new COBOL function to help integrate COBOL business processes and Web-oriented business processes by:
  • Simplifying the componentization of COBOL programs and enabling interoperability with Java components
  • Promoting the exchange and use of data in standardized formats, including XML and Unicode

This document will help you write and compile Enterprise COBOL programs. It will also help you define object-oriented classes and methods, invoke methods, and refer to objects in your programs.

This document assumes experience in developing application programs and some knowledge of COBOL. It focuses on using Enterprise COBOL to meet your programming objectives and not on the definition of the COBOL language. For complete information on COBOL syntax, see IBM Enterprise COBOL Language Reference.

For information on migrating programs to Enterprise COBOL, see IBM Enterprise COBOL Compiler and Run-Time Migration Guide.

IBM z/OS Language Environment provides the run-time environment and run-time services that are required to run your Enterprise COBOL programs. You will find information on link-editing and running programs in the IBM z/OS Language Environment Programming Guide and IBM z/OS Language Environment Programming Reference.

Click to Read More/Download

Labels:
Reactions:

Language Reference

This document presents the syntax of IBM Enterprise COBOL for z/OS and OS/390, referred to in this document as "Enterprise COBOL."
Use this document in conjunction with the Enterprise COBOL Programming Guide.
IBM extensions generally add features, syntax, or rules beyond those specified in ANSI and ISO COBOL standards. Extensions range from minor relaxation of rules to major capabilities, such as XML support, Unicode support, object-oriented COBOL for Java interoperability, and DBCS character handling.
Appendix A, "IBM extensions" in topic APPENDIX1.1, lists IBM extensions. The rest of this document describes the complete language without identifying extensions. You will need to review the Appendix and the compiler options described in the Enterprise COBOL Programming Guide if you want to use only standard language elements.
Obsolete language elements are COBOL 85 Standard language elements that will be deleted from the next revision of the ANSI and ISO COBOL standards (referred to in this document as Standard COBOL.
Note: This does not imply that these elements will be eliminated from a future release of Enterprise COBOL.
The language elements that will be deleted from the next revision of the ANSI and ISO COBOL standards are:
ALTER statement
AUTHOR paragraph
Comment entry
DATA RECORDS clause
DATE-COMPILED paragraph
DATE-WRITTEN paragraph
DEBUG-ITEM special register
Debugging sections
ENTER statement
GO TO without a specified procedure name
INSTALLATION paragraph
LABEL RECORDS clause
MEMORY SIZE clause
MULTIPLE FILE TAPE clause
RERUN clause
REVERSED phrase
SECURITY paragraph
Segmentation module
STOP literal format of the STOP statement
USE FOR DEBUGGING declarative
VALUE OF clause
The figurative constant ALL literal, when associated with a numeric or numeric-edited item and with a length greater than one
Labels:
Reactions:

COBOL for OS/390 & VM Programming Guide

Welcome to IBM COBOL for OS/390 & VM, IBM's latest host COBOL compiler!
This version of IBM COBOL for OS/390 & VM is fully source and object compatible with COBOL for MVS & VM Version 1, with the exception of programs containing object-oriented language constructs, which must be recompiled to enable support for OS/390 SOMobjects(TM), as described below.
The following is a brief outline of the differences from the COBOL for MVS & VM product:
  1. Support has been added for Dynamic Link Libraries (DLLs). A DLL is a load module containing programs and data which can be accessed from other load modules. The DLL mechanism is the primary means used for packaging SOM class libraries. With this new support, object-oriented COBOL applications may be packaged using separate DLL load modules for the client programs and class definitions. Two new compiler options, DLLNODLL and EXPORTALLNOEXPORTALL, are used to control the creation of DLLs. For details, see Chapter 20, "Building and Using Dynamic Link Libraries (DLLs)" in topic 4.2.
  2. Due to changes in the SOMobjects product that are delivered with OS/390® Release 3, changes in the JCL for building object-oriented COBOL applications are required:
  • The SOMobjects kernel and the SOMobjects class libraries must be accessed from the SOMobjects product DLLs, rather than being linked together with the COBOL application load module, as was required in the prior version. This requires changes to the JCL to specify appropriate COBOL compiler options for DLL support, the prelink step must specify (at least) the DLL definition side-decks for the SOM kernel and class libraries, and the SOM SGOSPLKD data set is no longer used in the SYSLIB concatenation of the prelink step.
  • The format of the SOM profile data set has changed, and the profile is now specified via the SOMENV DD statement rather than the SOMPROF DD.

For further details, see the OS/390 SOMobjects Programmer's Guide, and Chapter 16, "Using System Object Model (SOM)" in topic 3.2.

The INTDATE compiler option is no longer an installation option only--it can now be specified as an option when invoking the compiler.

Click to Read More/Download

Labels:
Reactions:

COBOL Language Reference

This book presents the syntax of COBOL for MVS & VM, COBOL Set for AIX, and VisualAge COBOL (collectively referred to in this book as IBM COBOL). To indicate platform-specific information, this book use the following methods:
  • Prefix the text with platform-specific indicators (for example, Under AIX, OS/2, and Windows...)
  • Add parenthetical qualifications (for example, (Workstation only))

Note: This book documents extensions for object-oriented COBOL. Object-oriented COBOL is not supported on VM.

Use this book in conjunction with the IBM COBOL Programming Guide for your platform.

Characters

The most basic and indivisible unit of the COBOL language is the character. The IBM COBOL character set includes the letters of the alphabet, digits, and special characters. The complete set of characters that form the IBM COBOL character set is shown in Table 1.

The basic IBM COBOL language is restricted to the character set shown in Table 1, but the content of nonnumeric literals, comment lines, comment entries, and data can include any of the characters from the character set of the computer.

Click to Read More/Download

Labels:
Reactions:

VS COBOL II Application Programming Guide

This manual helps you to create VS COBOL II programs; analyze and modify existing COBOL programs; and compile, link-edit, and execute VS COBOL II programs under MVS or CMS.
The purpose of this manual is to help you:
  • Create VS COBOL II programs
  • Analyze and modify existing COBOL programs
  • Compile, link-edit, and execute VS COBOL II programs.

Information on structured programming is included, as well as descriptions of the features available with VS COBOL II.

This manual is designed for the experienced COBOL programmer working in an MVS or CMS environment whose primary discipline is data processing and the development of applications. This book assumes that you know the COBOL language and how to develop an application program.

Click to Read More/Download

Labels:
Reactions:

VS COBOL II Application Programming Language Reference

This reference presents the syntax of VS COBOL II statements and the rules for writing source programs that are to be compiled by the VS COBOL II compiler. It is meant to be used as a reference in conjunction with VS COBOL II Application Programming Guide for MVS and CMS or VS COBOL II Application Programming Guide for VSE.
This language reference manual is designed for the experienced COBOL programmer whose primary discipline is data processing and whose task is the development of applications.
The VS COBOL II Application Programming Language Reference manual is organized for easy retrieval of language elements.
About This Manual-- Describes the VS COBOL II library and related publications, how to read the syntax diagrams, and the industry standards supported by VS COBOL II.
Part 1. VS COBOL II Language Structure-- Describes VS COBOL II characters, standard COBOL format, scope of names, and methods of data reference.
Part 2. VS COBOL II Program Structure-- Describes language elements of the Identification, Environment, and Data Divisions, plus an overview of the Procedure Division. Because the structure of the first three COBOL divisions is the same in most programs, the language element descriptions are presented in the order most programmers follow.
Part 3. Procedure Division Statements-- Describes the Procedure Division statements. Because the arrangement of statements in the Procedure Division varies from program to program, these statements are presented in alphabetical order.
Part 4. Compiler Directing Statements-- Describes the statements that direct the compiler to take a specified action.
Part 5. Appendixes-- Provides the following supplemental information:
Appendix A. VS COBOL II Compiler Limits
Appendix B. EBCDIC and ASCII Collating Sequences
Appendix C. ASCII Considerations
Appendix D. Source Language Debugging
Appendix E. COBOL Reserved Word List
Glossary--Defines technical terms.
Labels:
Reactions:

OS/390 FFST/MVS V1R2.0 Operations Guide

First Failure Support Technology* (FFST*) is an IBM* licensed program that provides immediate notification and first failure data capture (FFDC) for software events. IBM's SystemView* strategy incorporates FFST as part of its problem management discipline. This book applies to the following FFST products running in the specified environments:
  • FFST for Multiple Virtual Storage (FFST/MVS*) in a Multiple Virtual Storage/Enterprise Systems Architecture (MVS/ESA*) environment
  • FFST for Virtual Machine (FFST/VM*) in a Virtual Machine/Enterprise Systems Architecture* (VM/ESA*) environment

FFST/MVS also incorporates its own technology by including software probes in its own code. FFST/MVS processes these software probes using its internal FFDC function. When one of these internal software probes is triggered, FFST/MVS issues a symptom string that describes the event. This symptom string appears in the dump and in the generic alert. The dump is a member of a partitioned data set, which is specified in the FFST/MVS startup procedure. The FFDC messages describe the member name and the data set that contain the dump; you can format the dump using the FFST dump formatting program, EPWDMPFM. For more information, see Chapter 3, "Using FFST Output" in topic 3.0.

The software probes that FFST/MVS processes with its FFDC function can also be triggered for FFST/VM. However, FFST/VM does not have the FFDC function. As a result, when one of these software probes is triggered, FFST issues messages containing only the software probe's symptom string.

This book explains how to perform the following tasks:

  • Use commands to control FFST operation
  • Use the different types of FFST output to identify and analyze software events

The following people should read this book:

  • System operators who need to control FFST operation
  • Support personnel who use FFST output to identify and analyze software events

Click to Read More/Download

Labels:
Reactions:

EREP V3R5 Reference

The EREP Reference applies to EREP Version 3, Release 5.
The following operating systems can run EREP:
  • DOS/VS, DOS/VSE, VSE/ESA, and VSE/Advanced Functions--known collectively in this book as VSE systems.
  • VS2, MVS/370, MVS/XA, MVS/ESA, and OS/390mdash.known collectively in this book as MVS systems.
  • VM/370, VM/SP, VM/SP/HPO, VM/XA, and VM/ESA--known collectively in this book as VM systems.

If EREP 3.5 is not installed on your system, some of the information in this book may not apply. You can find out which level of EREP your system supports by checking the release number of the EREP tape last installed; the release number is in the System Control Programming Specifications, which accompany the EREP tape.

Note: New releases of EREP are always downward compatible. That is, the latest version of EREP always runs on your system. New releases also include new functions that you can only use if you have the latest version of your operating system; but generally, old functions are not eliminated. The same is true of this book, although some very old versions of EREP (for example, IFCEREP0) are no longer supported.

This publication is for people who manage and maintain data processing equipment in a system installation.

Click to Read More/Download

Labels:
Reactions:

IBM TotalStorage NAS Advantages of the Windows Powered OS

This IBM Redpaper describes the IBM TotalStorage NAS Advantages of the Windows Powered OS. The IBM Windows Powered NAS offers customers a comparitively low total cost of ownership when compared to the proprietary NAS offerings that are in the market today. The compelling features of IBM Windows Powered NAS that make low TCO feasible are shown in this paper.
TOC
  • What is Network Attached Storage (NAS)
  • NAS and the Windows Powered OS benefits
  • Total cost of ownershipSummary

Click to Read More/Download

Labels:
Reactions:

IBM System Storage Solutions Handbook

This IBM Redbook provides overviews and pointers for information about the most current IBM System Storage and TotalStorage products, showing how IBM delivers the right mix of products for nearly every aspect of business continuance and business efficiency. IBM TotalStorage products can help you store, safeguard, retrieve, and share your data.
  • First we introduce the basic storage solutions areas: information lifecycle management, infrastructure simplification, and business continuity.
  • Part 1 describes disk products, including the entire Disk Storage (DS) Series, from entry-level offerings, such as the DS300 and DS400, to mid-range with the DS4000 family and DS6000, to high end with the DS8000. It also includes the DR550.
  • Part 2 is an overview of tape products, covering tape drives, tape libraries, and virtualization products, including LTO and 3590, and 3592 technology.
  • Part 3 starts by describing storage networking infrastructure and protocols, and then presents the switches and directors to form SAN solutions.
  • Part 4 discusses the IBM TotalStorage software portfolio for open systems and includes Storage Virtualization products, such as the SAN Volume Controller, TotalStorage Productivity Center, Tivoli Storage Manager, and ETL Expert.
  • Part 5 describes the z/OS storage management software: DFSMS and DFSORT.
  • Part 6 is the appendixes, which cover standards, such as Storage Management Initiative Specification (SMI-S), Common Information Model (CIM), and Web Based Enterprise Management (WBEM); also discussed is redundant array of independent disks (RAID).

This redbook is intended as a reference for basic and comprehensive information about the IBM System Storage and TotalStorage products portfolio. This book provides a starting point when establishing your own enterprise storage environment.

Click to Read More/Download

Labels:
Reactions:

Text Search: Programming the Text Search Engine

This book describes the following interfaces:
  • The Text Search Engine application programming interface (API)
  • The Text Search Engine library service interfaces
  • The Text Search Engine text format

It explains how these interfaces can be used to:

  • Obtain Text Search Engine services from customer applications
  • Provide library services (document access) to Text Search Engine
  • Support additional text formats in Text Search Engine and exploit Text Search Engine support for multilingual documents.

This book contains information for application programmers who want to integrate Text Search Engine functions with customer applications, document repositories (libraries), or multimedia display services. It is written for application programmers who want to develop an application that can use the services of the Text Search Engine functions, or who want to develop programs that enable Text Search Engine to interface with a given document repository. All programming interfaces provided by Text Search Engine are for use with the C programming language. The Text Search Engine text format is a data interchange format, not a programming interface.

Click to Read More/Download

Labels:
Reactions:

z/OS V1R1.0 Encina Toolkit Executive Gd. and Ref.

This book introduces the z/OS Encina Toolkit Executive, which is part of z/OS Version 1 Release 1 Modification level 0. The purpose of this book is to help software designers and programmers use the Toolkit to develop transactional remote procedure calls (TRPCs) for z/OS Distributed Computing Environment (DCE) client-server applications.
On z/OS, you can write only ephemeral clients (those with no recovery service of their own). In combination with Application Support (AS), applications can use TRPCs to transactionally access IMS(TM) data from a workstation client, using the Recoverable Resource Management Services (RRMS), one component of which is z/OS Resource Recovery Services (RRS).
This book describes installation, administration, and use of the z/OS Encina Toolkit Executive.
This book is for system and network administrators who install and administer the z/OS Encina Toolkit Executive. It is also for system designers, application designers, host application programmers, and client application programmers who develop client-server applications using transactional RPCs in the Encina environment.
Labels:
Reactions:

z/OS V1R1.0 MVS Routing and Descriptor Codes

This book lists the routing and descriptor codes that IBM assigns to the messages that OS/390 components, subsystems, and products issue. Routing and descriptor codes are specified by the ROUTCDE and DESC keyword parameters on WTO and WTOR macros, which are the primary methods that programs use to issue messages. The routing code identifies where a message will be displayed. The descriptor code identifies the significance of the message and the color of the message on operator consoles with color (see "Message Color" in topic 2.4).
This book is intended for system and application programmers who want to direct messages to certain consoles in an installation with multiple console support (MCS).
Chapter 1, "Routing Codes" in topic 1.0 and Chapter 2, "Descriptor Codes" in topic 2.0 contain an introduction to routing and descriptor codes. These sections describe:
  • The meaning of each code
  • How these codes are specified
  • How the system uses these codes

For information on using routing and descriptor codes to route messages, see z/OS MVS Planning: Operations.

Chapter 3, "Message Identifiers and Associated Routing and Descriptor Codes" in topic 3.0 lists the routing and descriptor codes for each message identifier. The message identifiers are listed in alphabetical order according to their prefixes. Within a prefix section, the message identifiers appear in numerical order. The routing code appears to the right of the message identifier, followed by the descriptor code.

Click to Read More/Download

Labels:
Reactions:

z/OS V1R1.0 MVS Programming: Resource Recovery

This book describes RRS, the system-level resource recovery platform for z/OS. The book describes two major tasks:
  • How to use RRS services in authorized resource managers, such as database programs, and communications managers that manage distributed transactional communications.
  • How to manage RRS in an installation that runs resource managers that use RRS.

This book is for:

  • Programmers who design and code resource managers. These programmers need to know how to work with MVS system interfaces and how to work with databases.
  • System programmers responsible for managing MVS, including such tasks as starting and stopping system functions and troubleshooting. Data base administrators might also be involved in managing RRS.

Click to Read More/Download

Labels:
Reactions:

z/OS V1R1.0 MVS Programming: Product Registration

Product registration services allow products to register with MVS when they are running on a particular system. Other products can then use registration services to determine what products are running on a particular system.
Product registration provides an additional function for optional products, or elements, of z/OS. These optional products, which can be either products, product features, or combinations of product and feature, can use registration services to determine, based on a policy the customer sets, whether they are enabled to run on a particular system.
This book describes how to use registration services.
This book is for programmers who design and write, in assembler or C, programs that use registration services. It requires an understanding of how to work with MVS system interfaces.
Labels:
Reactions:

z/OS V1R1.0 MVS Device Validation Support

This book contains information that you need to write installation-supplied UIMs.
This book is intended for system programmers who are responsible for writing installation-supplied UIMs. The user must know the hardware and software configuration characteristics of the I/O unit that needs a UIM, and should be familiar with basic MVS concepts, with the Input/Output Configuration Program (IOCP), and with HCD.
Labels:
Reactions:

z/OS V1R1.0 MVS Using the Subsystem Interface

This book introduces you to subsystems, what they are and why you might want to write your own. It describes how to set up your subsystem and how to use it. MVS provides some services to help you build and use subsystems; these services are described in this book.
In addition, this book describes services provided by IBM subsystems that a program can use. The program need not be a subsystem to use these services.
This book is for system programmers or application developers who are writing a subsystem or requesting system services available through the subsystem interface (SSI).
This book assumes that the reader has extensive experience with MVS, is familiar with its basic concepts, can code JCL statements to execute programs or cataloged procedures, can code in assembler language, and can read assembler, loader, and linkage editor output.
Labels:
Reactions:

zSeries HiperSockets

This IBM Redbook positions the zSeries HiperSockets function. It offers a broad description of the architecture, microcode function, and operating systems support.
This document will help you plan and implement zSeries HiperSockets, and it provides information that focuses on the definitions needed to configure HiperSockets for the supported operating systems.
This redbook is intended for system programmers, network planners, and system engineers who will plan and install HiperSockets. A solid background in network planning and TCP/IP is assumed.
Labels:
Reactions:

z/OS V1R1.0 MVS System Messages (10 Books)

The MVS System Messages books primarily describe messages that are issued to the system operator at the system console and system messages that are logged. These include:
  • Operator messages issued by the BCP and DFSMS/MVS.
  • Log messages issued by the BCP and DFSMS/MVS.
  • Some SYSOUT messages issued by the BCP and DFSMS/MVS. SYSOUT messages are issued by utilities that normally run in batch, such as SPZAP.
  • Batch job messages issued by the BCP. Messages issued by JES2 or JES3 for batch jobs are in the JES messages books.

For the most part, messages issued at interactive terminals (like TSO/E and CICS terminals) are documented by the specific elements and products that support those terminals.

The titles of the MVS System Messages books indicate the range of message prefixes in the books:

If you do not know which book describes a particular message, try using LookAt (see "Using LookAt to look up message explanations" in topic PREFACE.3). Here are some of the books on that bookshelf:

The MVS System Messages books

For a list of message books sorted by message prefix, see "Message Directory" in topic PREFACE.6.3.

The system messages books are for all people who receive messages from the system. Usually, these people are system operators, system programmers, and application programmers who do any of the following tasks:

  • Initialize the operating system and its subsystems
  • Monitor system activity
  • Keep the system running correctly
  • Diagnose and correct system problems
  • Diagnose and correct errors in problem programs
Labels:
Reactions:

msys for Setup User's Guide

This book provides information you need to install and use Managed System Infrastructure for Setup (msys for Setup).
After reading this book, you will:
  • Understand what needs to be done before installing Managed System Infrastructure for Setup
  • Understand how to install Managed System Infrastructure for Setup
  • Understand how to use Managed System Infrastructure for Setup to set up a product (such as Parallel Sysplex®), that uses msys for Setup for its setup.
  • Know what other books to refer to when using Managed System Infrastructure for Setup.

This book assumes that you are familiar with, or have access to a person who is familiar with:

  • OS/390® and z/OS
  • OS/390 Security Server (RACF®)
  • DB2®
  • Communication Server IP (TCP/IP) and its FTP Server
  • ServerPac and SystemPac
  • Windows NT

This book further assumes that you have some conceptual knowledge of the Lightweight Directory Access Protocol (LDAP) although you by no means need to be an expert.

Click to Read More/Download

Labels:
Reactions:

Debug Tool User's Guide and Reference

Debug Tool combines the richness of the z/OS, System/370(TM), and System/390® subsystem environments with the power of Language Environment to provide a debugger for programmers to isolate and fix their program bugs and test their applications. Debug Tool gives you the capability of testing programs in batch, using a nonprogrammable terminal in full-screen or line mode, or using a workstation interface to remotely debug your programs.
This book contains instructions and examples to help you use Debug Tool to debug C, C++, COBOL, and PL/I applications running with Language Environment. Topics covered include preparing your application for debugging, accomplishing basic debugging tasks, and Debug Tool's interaction with different programming languages. A complete command reference section is also included.

You can begin testing with Debug Tool after learning just a few concepts:

  • How to invoke it
  • How to set, display, and remove breakpoints
  • How to step through your program

Debug Tool commands are similar to commands from the supported high level languages HLLs).

Click to Read More/Download

Labels:
Reactions:

z/OS MVS Product Management

This book describes the product management functions that MVS provides: measured usage and product registration.
For measured usage, SMF collects resource usage data (primarily CPU time) on an MVS system for any product that has identified itself and registered with SMF. The collected information, summarized by product version for an interval, is written in SMF record type 89 subtype 1 at specified intervals. (Some similar information is written in SMF record type 30 based on the SMF interval, but type 30 records include only the address space level information; system level information about a product appears only in record type 89.)
For product registration, SMF collects data for any product that has registered with MVS — identified itself and indicated that it is running on the system. The collected information, summarized by product for an interval, is written in SMF record type 89 subtype 2 at specified intervals. Optional elements that register with the system can be dynamically enabled.
This book is organized as follows:
  • Chapter 1. Usage Accounting — provides guidance information for measured usage accounting.
  • Chapter 2. Product Registration and Enablement — provides guidance information for product registration.
  • Chapter 3. Reporting Product Information — describes how to use IFAURP, the reporting program for product management.
  • Chapter 4. Usage Pricing Examples — contains multiple examples of how to use IFAURP for measured usage license charges.
  • Appendix A. ‘Type-Model’ Values for IBM and Non-IBM Processors — lists the supported IBM and non-IBM type and model values.
  • Appendix B. IFAURP Program Exit — describes the IFAURP program exit.

Click to Read More/Download

Labels:
Reactions:

z/OS MVS System Data Set Definition

This book explains how to define system data sets for a system running z/OS, including data sets required for DFSMSdfp.
This book is intended for anyone who needs to select and define system data sets for z/OS.
This book is divided into the following chapters:
  • Chapter 1. Selecting and Defining System Data Sets lists the system data sets that you might need to select, and explains how to define those system data sets through JCL and/or access method services.
  • Chapter 2. System Data Set Descriptions describes the master catalog and the system data sets.
  • Chapter 3. Using Data Sets from the Old Production System explains how to use some of the system data sets from an old production system.

Click to Read More/Download

Labels:
Reactions:

z/OS Parallel Sysplex Overview: Introducing Data Sharing and Parallelism in a Sysplex

This publication is about data sharing and parallelism in a sysplex and how it can meet the needs of your computing environment.
It introduces high-level concepts and information useful for anyone who will plan for, exploit, implement, or operate a sysplex that shares data and processes work in parallel.
This publication describes:
  • What a sysplex is and how it compares to existing non-sysplex computing environments
  • New features that enhance sysplex function
  • Work that a sysplex supports
  • Products that make up a sysplex
  • Various sysplex configurations and their benefits

Sysplex and Product Availability (“Roll-Out”) The sysplex is a large system computing environment that is evolving. Since the introduction of the sysplex, the coupling facility technology was developed to enhance sysplex capabilities. With a coupling facility in a sysplex, the participating MVS systems can do high performance data sharing. A sysplex with a coupling facility is called a Parallel Sysplex.

Note that this publication does not differentiate between a sysplex without a coupling facility and a sysplex with a coupling facility. When you see the termsysplex, understand it to mean a sysplex with a coupling facility (a Parallel Sysplex).

There might be changes to the implementation or availability of new products or functions. For information about availability of hardware and software sysplex support, consult your IBM representative.

Click to Read More/Download

Labels:
Reactions:

z/Architecture Principles of Operation

This publication provides, for reference purposes, a detailed z/Architecture* description.
The publication applies only to systems operating as defined by z/Architecture. For systems operating in accordance with the Enterprise SystemsArchitecture/390* (ESA/390*) definition, the IBMESA/390 Principles of Operation, SA22-7201, should be consulted.
The publication describes each function at thelevel of detail needed to prepare an assemblerlanguageprogram that relies on that function. It does not, however, describe the notation and conventions that must be employed in preparing such a program, for which the user must instead refer to the appropriate assembler-language publication.
The information in this publication is provided principally or use by assembler-language programmers, lthough anyone concerned with the unctional details of z/Architecture will find it useful.
This publication is written as a reference and should not be considered an introduction or a textbook. It assumes the user has a basic knowledge of data-processing systems.
All facilities discussed in this publication are not necessarily available on every model. Furthermore, in some instances the definitions have been structured to allow for some degree of extendibility, and therefore certain capabilities may be described or implied that are not offered on any model. Examples of such capabilities are the use of a 16-bit field in the subsystem-identification word to identify the subchannel number, the size of the CPU address, and the number of CPUs sharing main storage. The allowance for this type of extendibility should not be construed as implying any intention by IBM to provide such capabilities. For information about the characteristics and availability of facilities on a specific model, see the functional characteristics publication for that model.
Largely because this publication is arranged for reference, certain words and phrases appear, of necessity, earlier in the publication than the principal discussions explaining them. The reader who encounters a problem because of this arrangement should refer to the index, which indicates the location of the key description.
The information presented in this publication is grouped in 19 chapters and several appendixes:
Labels:
Reactions:

z/OS V1R1.0 MVS Planning: Workload Management

This book contains information to help you convert to MVS workload management, to use workload management, and to make the most out of workload management.
This book is intended for the system programmers, system analysts, and systems engineers who are responsible for developing a conversion plan for MVS workload management, and who are responsible for implementing MVS workload management.
Where necessary, this book references information in other books, using shortened versions of the book title. For complete titles and order numbers of the books for all products that are part of z/OS, see z/OS Information Roadmap.
Labels:
Reactions:

z/OS V1R1.0 MVS Workload Management Services

This book describes the MVS workload management services. The services are intended for programmers who write authorized programs.
This book is divided into two sections:
  • Using the Workload Management Services - This section provides an overview of the services, and how to use them.
  • Workload Management Services Reference - This section describes each service, its syntax, its parameters, and an example of how to issue it.

Programmers using assembler language can use the macros described in this book to invoke the services they need. This book includes some guidance information, and detailed information, such as the function, the syntax, and parameters needed to code the macros.

Click to Read More/Download

Labels:
Reactions:

Firewall Technologies

This book describes how to configure and administer the z/OS Firewall Technologies to prevent unwanted and unauthorized communication into or out of your secure network.
This document contains the following steps which are required to implement Firewall Technologies:
  • Pre-installation and planning
  • Installation
  • System and firewall configuration
  • Implementing firewall services

This book also includes configuration, commands, messages, examples and problem determination information for the z/OS Firewall Technologies.

Firewall Technologies functions are provided to a customer in both the SecureWay Communication Server for z/OS, and the z/OS Security Server.

Functions that are included with the SecureWay Communication Server are:

  • IP Packet Filtering
  • IP Security (tunnels)
  • Network Address Translation (NAT)

These functions are included as part of the IP Security feature of z/OS and are always available.

Functions that are included with the z/OS Security Server are:

  • Internet Security Association Key Management Protocol (ISAKMP) support
  • FTP proxy support
  • Socks server (daemon) support
  • Command Line Configuration/Administration
  • GUI Configuration/Administration

These functions (with the exception of Command Line Configuration/Administration) are not included as part of the z/OS base and are only available when the z/OS Security Server has been enabled. The Command Line Configuration/Administration support only requires that the z/OS Security Server is installed before it becomes available.

Click to Read More/Download

Labels:
Reactions:

z/OS HTTP Server Planning, Installing, and Using

The HTTP Server is a scalable, high-performance Web server that brings you state-of-the-art security, dynamic caching capabilities, advanced server statistic reporting, and site indexing. It allows you to exploit Java to build dynamic, personalized Web sites and use the Platform for Internet Content Selection (PICS) to both rate and filter Web content. With the HTTP Server, you can establish an effective presence on the World Wide Web, reach customers and suppliers around the world, and conduct secure electronic commerce.
The HTTP Server provides product documentation in softcopy formats only. The most current information is available on the Web site Library page at URL:
For a summary of available z/OS documentation and online information, see the z/OS Information Roadmap. You can access z/OS documentation on the Web at URL:
Labels:
Reactions:

WebSphere Application Server for OS/390 - Application Server Planning, Installing, and Using

WebSphere Application Server for OS/390 is a Java-based servlet engine that lets you achieve your "write once, use anywhere" goal for servlet development. It runs as a plugin to the following OS/390 Web servers:
  • IBM HTTP Server Version 5.3
  • IBM HTTP Server Version 5.2
  • IBM HTTP Server Version 5.1
  • Lotus Domino Go Webserver Version 5.0

For information on Web server documentation, see the table in Required OS/390 Web server.

Click to Read More/Download

Labels:
Reactions:
Subscribe to: Posts (Atom)

Followers

Search for unlisted Ebooks
Posted by at

1 comment:

  1. Orion GovernanceNovember 10, 2020 at 2:03 AM

    Great post. lots of creativity and energy, very useful things you have share here. Thanks for your wonderful sharing.
    Data trust solutions
    Mainframe migration

    ReplyDelete

Subscribe to: Post Comments (Atom)