EXEC CICS QUERY SECURITY control

Default CICS CLASS used:

Restype: DB2ENTRY Class DB2ENTRY

FILE Class FCICSFCT

JOURNALNAME Class JCICSJCT

JOURNALNUM Class JCICSJCT

PROGRAM Class MCICSPPT

PSB Class PCICSPSB

SPCOMMAND Class CCISCMD

TDQUEUE Class DCICSDCT

TRANSACTION Class TCICSTRN

TRANSATTACH Class ACICSPCT

TSQUEUE Class SCICSTST

A History of CICS

1968
* CICS/OS introduced as program offering

* Designed to support 50 BTAM terminals

* Supported out of Palo Alto, CA

* Not expected to last more than a few years

* Assembler macros that supported a limited number of functions

1974
* CICS/VS 1.0 introduced* Single address space or partition monitor

* Introduction of management functions

* Support for DOS/VS, OS/VS1, and OS/VS2

* Macro Level only

* HLL supported through pre-processor

1976
* CICS/VS 1.3

* Support moved to Hursley in exchange for PL/1

* Introduction of command level

* Introduction of recovery/restart

1978
* CICS/VS 1.4

* Introduction of ISC

* IBM® Statement: New functions will be through command level

1980
* CICS/VS 1.5

* Introduction of MRO

1983
* CICS/VS 1.6, and 6 months later 1.6.1

* Introduction of RDO for PPT and PCT entries

* Last release to provide the same functionality across all operating systems

* XA functions are provided

* VSAM subtasking introduced

1986
* CICS/VS 1.7

* AUTOINSTALL + JES Spool Interface support introduced

* VTAM® terminals now RDO definable

* ISAM support dropped

* File control program and other management module rewritten

* The new code became OCO* IBM again warns its customers about Macro Level

1987
* CICS/MVS® 2.1

* Some performance improvements over 1.7

* Introduction of XRF

1989
* CICS/ESA® 3.1.1

* Macro Level support dropped for HLL programs

* Totally new architecture

* Multiple TCBs

* Many old functions dropped

1991
* CICS/ESA 3.2

* Macro Level support dropped for all languages

* Another rewrite for DFHFCP

* CICS security as known (DFHSNT) is eliminated

* More old functions are dropped

1992
* CICS/ESA 3.3

* Storage protection feature for CICS/ESA domain storage

* Introduction of Dynamic Link function

* Shared Data Tables

* Distributed Program Link

* Front End Programming Interface

1994
* CICS/ESA 4.1

* Transaction Isolation (Storage protection)

* MRO using Enhanced Cross System Coupling Facilities (XRF)

* Dynamic transaction routing among Parallel Transaction Servermachines

1995
* CICS/VSE® 2.3

* Enhanced programmer interfaces allowing for the replacement of macro level calls

* Support for LE for VSE/ESA and associated languages

* A tool to aid in the migration of customers from the use of internal CICS security to an external security manager (ESM)

1996
* CICS Transaction Server for OS/390® 1.1

* A new domain for logging and journaling - the CICS log manager

* A new domain for recovery - the CICS recovery manager

* A new domain for temporary storage

* RDO for transient data destinations

* Addition of the EXEC CICS CREATE SPI command for the creation of CICS resource definitions for a sysplex-wide systems management product

1997
* CICS Transaction Server for OS/390 1.2

* Introduction of DASDONLY logging

1998
* CICS Transaction Server for OS/390 1.3

* Parallel Sysplex® support

* Coupling facility data tables

* RDO for temporary storage

* Long temporary storage queue names

* Autoinstall for consoles

* CICS business transaction services (BTS)

* Open transaction environment (OTE)

* Support for the Java™ Virtual Machine (JVM)

* Support for IIOP requests inbound to Java application programs.

2000
* CICS Transaction Server for VSE/ESA™ 1.1.1

* Exploitation of ESA/390 subsystem storage protection

* Extensive Virtual Storage Constraint Relief

* Expanded Application Programming Support including a new External CICS Interface (EXCI) and a Front End Programming Interface (FEPI)

* System Management enhancements including Resource Definition Online (RDO) for files

* Shared data tables for improved performance and availability

* The CICS Web Interface (CWI) which provides direct access to CICS applications from the World Wide Web environment. This will be available from the first quarter of 2000

* The CICS 3270 Bridge, which provides an interface to run 3270-based CICS transactions without a 3270 terminal.

* Inclusion of REXX for CICS, from the fourth quarter of 1999.

* Inclusion of CICS/DDM as an optional no-charge feature* Inclusion of Report Controller Facility (RCF) without extra charge.

2001
* CICS Transaction Server for z/OS® 2.1

* Support for the industry-standard Enterprise JavaBeans (EJB) architecture, enabling CICS to act as an EJB server

* Facilities for the generation of new EJB applications, or for the reuse or incorporation of existing applications and data in an EJB solution

* Enhancements to the facilities for network connectivity in support of e-business enablement, and to Java programming under CICS

* Extensions to facilities for applications based on procedural programming models

* Significant extensions to CICSPlex® SM

2002
* CICS Transaction Server for z/OS 2.2

* Enhanced support for Enterprise Java, and session bean support that conforms to the J2EE Enterprise JavaBeans (EJB) architecture.

2003
* CICS Transaction Server for z/OS 2.3

* Enhanced Java capability including performance improvements, support for Java SDK 1.4, the Common Client Interface (CCI) Connector for CICS TS, and the addition of CICS Web Support to the JCICS classes

* Improved support for development of applications, including interactive debugging

* Further connectivity options, including new security functions, and the recently-introduced SOAP for CICS optional feature

* Enhancements in the area of availability, including workload balancing of the 3270 Bridge using CICSPlex(R) SM

* Important performance improvements in CICS-DB2 attachment

2005
* CICS Transaction Server for z/OS 3.1

* Major new capabilities are provided in the areas of Web services, HTTP function, and security

* C/C++ capability is enhanced by support for XPLink

* CICS Web API commands are now threadsafe* OTE function has been extended

* Language Environment-enabled Assembler applications are supported

* A new mechanism is provided for inter-program data transfer

* The Information Center has moved to the Eclipse platform

* Functional and usability improvements are provided to the CICSPlex SM Web User Interface, enabling systems to be fully managed without the TSO End User Interface

* New batch update mechanism is provided for the CICSPlex SM data repository

2007
* CICS Transaction Server for z/OS 3.2

* Application Connectivityo Web services standards, interoperability profiles, large messages, and data mappingo Intercommunications over TCP/IPo HTTP and TCP/IP management and performance

* Application Reuseo 64-bit storage for CONTAINER datao CICS integrated translator support for C and C++o Java enhancements

* Service Managemento On-line management of program librarieso Enterprise Workload Managero CICSPlex SM Web User Interface help, usability, and MAP supporto CICS-WMQ adapter installation and management

* Architectural Enhancementso Capacity of VSAM ESDS files >4GB, shared data tables >2GB, and CICS regions in a Sysplexo Trace, monitoring, and statisticso Threadsafe core APIs for accessing VSAM files, journals, and WebSphere® MQ

...taken from an IBM site
http://www-1.ibm.com/support/docview.wss?rs=1083&context=SSGMGV&dc=DB520&uid=swg21025234&loc=en_US&cs=UTF-8&lang=en&rss=ct1083other

How can I find out what jobs are filling the JES2 spool

Here is a selection of useful JES2 commands:
$djq,spl=(%>5) Display all jobs which occupy more than 5% of the spool
$djq,a>5,q=ppu Display all jobs on the print/punch queue more than 5 days old
$djq,q=ppu,type=tsu Display all TSUs on the print/punch queue
$djq'jobname',spl Display spool percent occupied by the named job
$djq,q=ppu,userid Display userid associated with jobs on print/punch queue
$pjq,a>5,q=ppu Purges all jobs on the print/punch queue more than 5 days old
$pjq,q=ppu,type=tsu Purge all TSUs on the print/punch queue
$da,x Displays all jobs, including TSU and STC
$pjnnnnn Purge JOB number nnnnn
$psnnnnn Purge STC number nnnnn
$ptnnnnn Purge TSU number nnnnn
$dspl Display percent spool used
$ta wlog,t=23.58,i=86400,'$vs,''W L''' Automatically spin SYSLOG to sysout L once per day
$dos'syslog',crtime,age,rec,odisp,q Display all SYSLOG output groups on spool
$pos'syslog',a>5 Delete SYSLOG output groups more than 5 days old

How do I get step condition codes to print in the JES2 job log

Install the SMF exit IEFACTRT. The source is in SYS1.SAMPLIB(IEEACTRT).

1. Run this job to install the exit in a linklist library:

//SPSMFXIT JOB CLASS=A,MSGCLASS=X,MSGLEVEL=(1,1),NOTIFY=&SYSUID
//ASMXIT EXEC HLASMCL,REGION=4M,COND.L=(0,NE,C),
// PARM.L='LIST,LET,NCAL,XREF,RENT,REUS'
//C.SYSLIB DD DSN=SYS1.MACLIB,DISP=SHR
// DD DSN=SYS1.MODGEN,DISP=SHR
//C.SYSIN DD DSN=SYS1.SAMPLIB(IEEACTRT),DISP=SHR
//L.SYSLMOD DD DSN=USER.LINKLIB(IEFACTRT),DISP=SHR,UNIT=,SPACE=

2. Update your SMF parameter member SMFPRM00 in USER.PARMLIB. You need SMF recording ACTIVE, you need to record at least type 30 records which drive the IEFACTRT exit, and of course you need to specify that exit IEFACTRT is active. Here is an example SMFPRM00 member:

ACTIVE /* ACTIVE SMF RECORDING */
DSNAME(SYS1.MAN1,
SYS1.MAN2,
SYS1.MAN3)
NOPROMPT /* DO NOT PROMPT OPERATOR */
REC(PERM) /* TYPE 17 PERM RECORDS ONLY */
MAXDORM(3000) /* WRITE IDLE BUFFER AFTER 30 MIN */
STATUS(010000) /* WRITE SMF STATS AFTER 1 HOUR */
JWT(2400) /* 522 AFTER 24 HOURS */
SID(&SYSNAME(1:4)) /* USE SYSTEM NAME FROM IEASYM00 */
LISTDSN /* LIST DATA SET STATUS AT IPL */
SYS(TYPE(14:19,30,62:69),NOEXITS,NOINTERVAL,NODETAIL)
/* WRITE ONLY DATA MANAGEMENT RECORDS, TAKE NO EXITS. */
/* NOTE: JES EXITS CONTROLED BY JES , THERE IS NO */
/* DEFAULT INTERVAL RECORDS WRITTEN AND ONLY SUMMARY T32 */
/* RECORDS AS A DEFAULT FOR TSO. */
SUBSYS(JES2,EXITS(IEFACTRT))
/* WRITE RECORDS ACCORDING TO SYS VALUE, TAKE ONLY IEFACTRT EXIT. */
/* USE ALL OTHER SYS PARMETERS AS A DEFAULT. */

3. Enter this MVS command to activate the updated SMF parameters:

SET SMF=00

4. Enter these MVS commands to activate the exit:

F LLA,REFRESH
SETPROG EXIT,DELETE,EXITNAME=SYSJES2.IEFACTRT,MODNAME=IEFACTRT
SETPROG EXIT,ADD,EX=SYSJES2.IEFACTRT,MOD=IEFACTRT,DSN=USER.LINKLIB