Sie sind auf Seite 1von 50

(E)JES Update

Ed Jaffe
Phoenix Software International

5 August 2014
Session Number 16262

Insert
Custom
Session
QR if
Desired.
New Release Support Policy Better Aligns with
z/OS Release Strategy
• Prior to April 2014:
– Release stabilized 3-6 months after becoming N-2
– Diagnostic technical support (i.e., dump analysis) ends two
years after Release Stabilization.
• Regular, annual releases meant these events occurred
2 ½ and 4 ½ years after GA respectively.
• Beginning April 2014:
– Release stabilized three years after GA.
– Diagnostic technical support (i.e. dump analysis) ends four
years after GA.

2
Compatibility Matrix
Operating
System
V5R4
09/14
V5R3
09/13
V5R2
09/12
V5R1
09/11
• V5R4 planned GA next
month.
z/OS 2.1 JES2/JES3 JES2/JES3 JES3
• V5R3 was released
z/OS 1.13 JES2/JES3 JES2/JES3 JES2/JES3 JES2/JES3
September 2013.
z/OS 1.12 JES2/JES3 JES2/JES3 JES2/JES3 JES2/JES3
• New release required to
z/OS 1.11 JES2/JES3 JES2/JES3 JES2/JES3 JES2/JES3
support z/OS 2.1 JES2
z/OS 1.10 JES2/JES3 JES2/JES3 JES2/JES3 JES2/JES3
• z/OS 2.1 JES3 support
z/OS 1.9 JES2/JES3 JES2/JES3 JES2/JES3 JES2/JES3 rolled back to V5R2.
z/OS 1.8 JES2/JES3 JES2/JES3 JES2/JES3 JES2/JES3 • Based on the new policy,
z/OS 1.7 JES2/JES3 JES2/JES3 V5R3 will not be stabilized
z/OS 1.6 JES2/JES3 until September 2016. 
• Note: z/OS 1.12 goes out
of IBM support beginning
4Q14.
3
(E)JES V5R4
Highlights
Asynchronous Multisystem Displays
• Remote queries are
C
launched. CAS collects
LAUNCH
REMOTE
QUERIES A
and readies the data. S

• Local data is collected. COLLECT


LOCAL
DATA
S
E
• Remote data is retrieved R
V
from CAS.
COPY
REMOTE E
DATA
R
• Optional sorting of S

tabular rows occurs as SORT


?
SORT
TABULAR

normal
ROWS

• Side effect: STD sort DISPLAY


RESULTS
TO USER
now always places
current system first.
5
64-bit Addressing Mode
• Most (E)JES programs will run in 64-bit addressing mode.
• (E)JES will be among a very select few HLASM-authored
z/OS software products that can make this claim.
– Perhaps the only one?
• Areas of known virtual storage constraint will be moved
above the 2G bar. Others will move as needed.
• User exits will continue to be given control in 31-bit mode
(via BASSM) and all data areas passed to them will still
reside below the 2GB bar. Return is now via BSM.
– A standard 144-byte F4SA save area is passed and the
distributed user exit linkage has been updated to use it.
– This allows user exits to use “grande” instructions and/or
switch to 64-bit mode if they so choose. Not required.

6
Parallelism
• Much has been said about the physics of existing chip
technology having reached the point where single core
speeds will no longer increase as they have done
historically.
• We have implemented some new highly-parallel,
algorithms to the parts of our code that are the highest
CPU consumers. The results so far are encouraging!
• For example, we observed that the clock time required for
Expensive Task X was reduced by 64% by splitting the
work across three dispatchable units (SRBs).

• Moore's Law be Damned!! ?

7
(E)JES Web Production Release
• Performance should now satisfy users accustomed to the
response time characteristics of the (E)JES ISPF
interface.
• Any operation that processes more than one screen worth
of data e.g., sort, search, etc. are all now performed at the
host using (E)JES API facilities.
• No more reliance on Infragistics igGrid UI.
– Always intended as a temporary technology bridge.
– No more tabular pages concept. Now everything is line/row
oriented, just like other (E)JES interfaces.
• Vertical scroll processing is now fully virtualized.
• Time-oriented browser support (OPERLOG).
• Command pop-up when slash key pressed.

8
API Improvements
• New flag (EJESApiUPHiddenTC) requests tabular columns
array include “hidden” columns (those with zero-length title).
• A new indicator (EJESApiTCScroll) set when a tabular column
can scroll horizontally. This lets the caller know where the scroll
point is positioned without requiring use of the ARRANGE
display.
• EJESApiUlgCART added to provide Command and Response
Token (CART) of last command issued.
– Can be matched up with lines on ULOG to obtain a complete
command response.
• All commands now generated with CART.
– Previously, only commands for which an in-line command response
was expected – and CRDELAY>0 – were assigned a CART.

9
Group ARRANGE by Column Name
• Some (E)JES tabular displays have grouped columns.
– Multiple contiguous columns that appear under a single title.
• Column groups can be moved on the ARRANGE dialog.
• Previously, any attempt to use the ARRANGE command to
move a grouped column by name would generate an error
message. ARRANGE using the title was required.
• In this release, any grouped column moved by the
ARRANGE command will move the entire group.

10
QUERY AUTH DISPLAY
• QUERY AUTH listed authorized commands, but provided
no understanding of menu structure.
• This release implements an optional DISPLAY keyword
that will return the menu structure and commands within.

11
Initial LOG Horizontal Positioning
• The JES2 SYSLOG, JES3 SYSLOG and OPERLOG
displays have “smart” routines for setting initial horizontal
display position.
• An assumption was made that these routines need not be
called when 3270 screen width was greater than 80; far
left positioning was fine. That assumption was wrong. 
• In this release, far left positioning is used only when the
3270 screen is wide enough to display all of the data.

12
Title Line Suppression for Tabular Extract
• Traditionally, three lines appear at the beginning of a
tabular extract:
– Line one is identical to the 3270 screen title line.
– Line two contains the tabular column titles.
– Line three contains the tabular column title underscores.
• Skipping over those three lines, adjusting record count,
etc., can be inconvenient for post-processing programs.
• The new NOTITLES keyword on the EXTRACT command
will suppress generation of these three lines.
• Note: previously, an empty data set was not possible. It is
now.

13
Rename of TP Monitor Parts
• Previously, TP Monitor parts started with GA, PHNX or
CAM (their “native” names).
• That had the potential for conflict when multiple, unrelated
products with TP Monitor componentry were co-located or
co-executed.
• In this release, all TP Monitor parts shipped with (E)JES
start with QPX.

14
MXGEJES
• (E)JES produces SMF records, but provides no code to help
analyze them. (Left as an exercise for the customer…)
• MXG is a product from Merrill Consultants used for analyzing
z/OS SMF records. See: http://mxg.com/
• MXGEJES is “a standalone MXG code execution” that will help
analyze and report the contents of (E)JES SMF records.
• (E)JES supports two SMF record formats:
– Format 0 is the default.
– Format 1 uses self-describing triplets for various sections of the
record and is the format required by MXGEJES.
• MXGEJES comes with MXG (32.047+); not with (E)JES.
• Many thanks to Barry Merrill for his help in understanding how
SMF records should be formatted, for authoring the MXGEJES
tooling, and for making it available to our customers. 

15
Highlights from the
(E)JES V5R3 Press
Release
(E)JES V5R3 Press Release
• z/OS 2.1 Support
• EJESMAIL utility
• DASD Extract Cataloged Data Set List
• Filtering using system symbols
• InfoCenter Integration
• CA Chorus Software Manager Install/Service
• (E)JES Web Technology Preview
“The timing of the availability and the functionality included in this
release should provide a smooth migration path for customers
interested in becoming early adopters of the first new version of IBM's
flagship operating system for System z in over twelve years.”
– Ed Jaffe, Chief Technology Officer

17
z/OS 2.1 Support
• MinOSLvl column and W-OSLVL delay reason
• JES2 eight-character job classes and job class groups
• JES3 support for in-stream data in JCL procedures

18
EJESMAIL Utility
• EJESMAIL is a new REXX exec written to help customers
send textual job output via email. It is not part of the
Customer Application Infrastructure (CAI), but it does rely
on some of the CAI utilities.
• EJESMAIL can be invoked as a TSO/E foreground
command, from the z/OS UNIX OMVS command prompt,
as a batch job step, or under System REXX.
• EJESMAIL supports the same three mail transport agents
supported by the CAI email plug-in and utilities: NJE,
direct sockets, and XMITIP (from Lionel Dyck).
• EJESMAIL can be a convenient way for a batch job to
email some or all of its own output.

19
EJESMAIL Usage Examples
//***************************************/
//* Email Output of our Job to JOEUSER */
//***************************************/
//EMAILJOB EXEC PGM=IKJEFT01
//SYSEXEC DD DSN=EJES.SEJEEXEC,DISP=SHR
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
EJESMAIL mysystem@mycompany.com joeuser@mycompany.com +
CC: edjaffe@phoenixsoftware.com paulscott@phoenixsoftware.com +
(NJE Subject:"Output from &JNA" +
Please find attached the output from job &JNA. Thanks!
/*

//***************************************/
//* Email LISTVTOC Output to JOEUSER */
//***************************************/
//EMAILRPT EXEC PGM=IKJEFT01
//SYSEXEC DD DSN=EJES.SEJEEXEC,DISP=SHR
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
EJESMAIL mysystem@mycompany.com joeuser@mycompany.com +
(XMITIP DD:SYSPRINT Subject:"Result of LISTVTOC command"
//NOTEDD DD *
Dear Joe,

The LISTVTOC output you requested is attached. We hope it


provides you with the enlightenment you seek.

Thanks,

The Management
/*
20
DASD Extract Cataloged Data Set List
Enhanced Symbolic Substitution in Filters
(Primary, Additional, Metafilters, etc)
• V3R5 introduced Environment Variables—symbols derived
from the current environment that can be used in filters
– These have been renamed to (E)JES Environment Symbols
• Beginning in this release, z/OS system symbols can also be
used. If an ampersand remains after substitution of (E)JES
environment symbols, a z/OS symbol substitution service is
invoked to process the string.
• Both static (e.g., &SYSNAME) and dynamic (e.g., &WDAY)
symbols are supported
Substitution for Metafilters is Dynamic
• Most filters are substituted immediately when the filter is
established. Substitution for metafilters occurs at the time
the filter is actually used. What you type is unchanged.
InfoCenter Search Integration Under ISPF
• F6 is now assigned to the INFO command
– Previously F6 was assigned to the BOOK command
– BOOK command moved to F18 (Shift+F6)
• INFO command with no explicitly-specified search words
and cursor not positioned results in display of InfoCenter
Search pop-up
– Search words can be entered and search launched
– InfoCenter parameters pop-up is requested by pressing F6
on InfoCenter Search pop-up
• INFO command with explicitly-specified search words or
cursor positioned to word within scrollable area initiates an
InfoCenter search

25
26
InfoCenter Setup Pop-up

• Accessed via F6 from InfoCenter Search pop-up


• Specify URL of InfoCenter server. If not specified, defaults
as follows based upon the current z/OS release:
– http://publib.boulder.ibm.com/infocenter/zos/v2r1
– http://publib.boulder.ibm.com/infocenter/zos/v1r13
– http://publib.boulder.ibm.com/infocenter/zos/v1r12
– http://publib.boulder.ibm.com/infocenter/zos/v1r11
• Scope defaults to All Topics
• Browser name and directory not required for Windows

27
28
InfoCenter Search Behavior
• If ISPF Workstation Agent (WSA) connected, web browser
is launched on local workstation to initiate the InfoCenter
search
– Connect WSA using WSCON command
– Do not confuse WSA with ISPF C/S; GUI not required
• If WSA not connected, URL is displayed on 3270 screen
– Most modern 3270 emulators provide “hot spot” support for
URLs displayed within the 3270 presentation area
– Clicking on the URL usually results in a launching of web
browser to process the URL

29
30
Installation via Chorus Software Manager from
CA Technologies

FTP or PFI
HTTP EJESDNLD
Materials

Input to
EJESPFI
• Install continues to use SMP/E

existing PFI download Yes


and unlock technology. CSM?
Create
CSM Input
Input to
CSM
• Install path diverges No
based on user response.
Full Install Partial
• Input to CSM created by EJESJCLU Library EJESJCLU
EJESPFI utility in z/OS
UNIX directory of choice. Install
With CSM
• JCL customization has
fewer replaceable keys
and sample jobs for Submit
all jobs
Submit
some jobs
CSM install.
32
Eleven
prompts
disappear for
CSM install

33
PTF and USERMOD Transformation
++USERMOD(EJESLIC) REWORK(2013069) .
• For traditional install, PTFs ++VER(Z038) FMID(QEJ5300) .
++SRC(EJESLIC) .
and USERMODs are * REL=V5R3 GRACE=2013-01-01
*---+----1----+----2----+----3----+----4--
delivered as batch JCL. --+----5
EJESGLIC
DATA=001307508CD994D2F181590816EF82FF
• When using CSM install, EJESGLIC DATA=C4C4E0
EJESGLIC CKSUM=0000021813
these members are END ,

transformed into pure


SMP/E input and renamed. ++USERMOD(EJESLIC) REWORK(2013069) .
++VER(Z038) FMID(QEJ5300) .
– PTFs renamed from ++SRC(EJESLIC) .
* REL=V5R3 GRACE=2013-01-01
EJES$xxx to PTFCxxx *---+----1----+----2----+----3----+----4---
-+----5
– USERMODs renamed from EJESGLIC
DATA=001307508CD994D2F181590816EF82FF
EJES$xxx to UMODxxx EJESGLIC DATA=C4C4E0
EJESGLIC CKSUM=0000021813
END ,
//

34
Some Some are
members are transformed
not used and renamed

35
36
(E)JES Web Technology Preview

• The (E)JES Web Technology Preview is a browser-based


interface to (E)JES implemented in Java.
• The initial release, which we classify as a technology
preview, allows many basic (E)JES functions to be
performed.
• Our intent is to create a de-Facto interface to (E)JES for
users that are uncomfortable navigating traditional 3270
interfaces.
• The REST API backing this technology will provide a
framework for the creation of Eclipse plug-ins, mobile
applications, and other web services clients.
(E)JES Web Technology Preview

• (E)JES Web is built on top of the (E)JES Java API.


– The (E)JES API (all flavors) keeps improving as a result of
this effort.
• IBM has given z/OS Java highly-preferential treatment in
System z hardware/software design and customer terms
and conditions. This trend is expected to continue, making
z/OS Java a solid language/platform choice with good
investment protection for the foreseeable future.
The Updated (E)JES “Solar System”
INTERACTIVE
•ISPF application TSO Users
•TSO cm d processor (TPUT)
PHOENIX
•Th read-safe CICS transaction
•Ph oen ix TP Mon itor transaction Users Batch Job
•Wi n dows PC v ia (E)JES workstation
com pon en t client/server
(No Language)
•Web i n terface under Apache Tom cat TSO ISPF BATCH
Cmd Proc Commands
PROGRAMMABLE CLIST Language
•TSO cm d processor (GET/PUTLINE)
•MV S program (QSAM GET/PUT)
PHOENIX TSO
•EJESREXX environment for REXX
•ISFCA LLS en vironment for REXX
CLIST
(ru n SDSF REXX execs!) EJESTSO
•EJESJA VA for Java programs BATCH Windows
•EJESA PI callable from HLA SM,
C/C++, COBOL, PL/I, etc. (REXX and
CLIST PC Users
Jav a interfaces are API exploiters.)

CICS Users
EJESCICS
(E)JES EJESLNK
Evo N800w

EJWSMVS
mobile workstation

EJESCICI
“CORE” EJWS4WIN
CICS

EJESREXX REXX Language


EJESAPI
HLASM
TSO
EJESISFX REXX
C/C++
(ISFCALLS) Console
EJESJAVA
IRXJCL Operators
COBOL REXX
High Level SYSREXX
Languages PL/I WWW Users
Apache
JAVA
Tomcat
Server Evo N800w

mobile workstation
(E)JES Web Deployment
• Each running instance of (E)JES Web must be deployed.
• A sample JCL procedure is provided. The same procedure
can be shared by multiple deployments.
• Batch JCL is provided to create a small, read/write zFS file
system for running an instance.
• A z/OS UNIX OMVS shell script prompts for eight basic
parameters—most of which default naturally.
• The script populates the target instance file system and
creates a parmlib member unique to the instance.
• An (E)JES Web instance typically runs as a started task.
• An instance is stopped via the MVS STOP command.

45
CPU Performance
Benchmark Results
JES2 CPU Performance Benchmark:
Between 3.5x and 12.5x

30
SSI 80
25

20

15 (E)JES
Slow
10 (E)JES Refresh
Rapid
5 Refresh
0
JES2 Held Output Display
JES3 CPU Performance Benchmark: 5.4x

SSI 80
100
90
80
70
60
50
40
30
(E)JES
20
10
0
JES3 Held Output Display
Performance Differences in Perspective
• The benchmark savings occur using apples-to-apples
measurements with TCB-mode only, GCP execution.
• Customers with zIIP processor(s) will gain additional
benefits.
• Not only does (E)JES use far less CPU than any SSI 80
exploiter, but nearly all of it is eligible for redirection to zIIP.
• In the case of SSI 80, none of the CPU resources are
eligible for zIIP redirection—even for customers with zIIP
processors available.

JobName CPU-Time
--------/--------
ACPU-Time
---------
zIIP-Time
---------
GCP-Time
--------
zICP-Time
---------
94%
JOEUSER 00:06.15
JOEUSER 00:07.16
00:12.20
00:29.12
00:05.94
00:21.71
00:05.94
00:06.91
00:00.00 BEFORE
00:00.00 AFTER
Offload
JOEUSER 00:01.01 00:16.92 00:15.77 00:00.97 00:00.00 DIFFERENCE
Questions?