The document describes features of Xpediter/CICS 6.8 and 7.0 releases. Key features include expanded language environment support, restricted operating modes, support for High Level Assembler, storage protection for CICS commands, usability enhancements, and Year 2000 compliance for release 6.8. Release 7.0 added features such as logging of file utility changes, scripting of commands, trap by user ID, four-digit year display, enhanced find command, and hypertext help.
2. Kanbay
Incorporate
Xpediter/CICS 6.8 and 7.0 Features
Expanded Language Environment Support :
Releases 1.4 and above of Language environment are now supported, including
support for trap unhandled conditions. User condition handlers are also
supported with language environment 1.5
Restricted Operating Modes :
XPEDITER’s three new operating modes let you tailor its implementation to suit
the specific requirements of different CICS regions.
High Level Assembler : Release 6.8
adds toleration support for HLAR Release 2. XPEDITER now also supports the
advanced using constructs of HLA Release 1, plus mixed case listing heading
and the LIST option in Release 2.
3. Kanbay
Incorporate
Xpediter/CICS 6.8 and 7.0 Features
Storage Protection of CICS Command Level Command :
XPEDITER/CICS now provides extended storage protection capabilities that
let you prevent violation caused by invalid information being passed to CICS
command level commands.
Additional Usability Enhancements :
COBOL 88 level support
Display of global table parameter values
Expanded Source Listing screen status line
Cancel capability in the DL/I file utility
Ability to disable abend trapping
Year 2000 Compliance.
4. Kanbay
Incorporate
Xpediter/CICS 7.0 New Release Features
Logging of File Utility Changes:
The new log Facility enables tracking of changes to supported resources made with
XPEDITER’s File Utility. Log data is a Generation Data Group dataset and can be output
in a number of different formats.
Scripting of XPEDITER Commands: XPEDITER’s
supports IBM’s newest release of CICS Transaction Server for OS/390 and features
improved display of shared temporary storage.
Trap by User ID:
Release 7.0 allows traps and brakpoints to be set by user ID.
Four-digit Year Display :
2000 compliance is enhanced by the display of all program dates in unambiguous
DDMMMYYY Format.
Added Find Command Features:
The Xpediter FIND command now supports hex and test strings, as well as character
strings on terminals that allow mixed case input.
5. Kanbay
Incorporate
Xpediter/CICS 7.0 New Release Features
Hypertex Help : The Help facility in XPEDITER/CICS now uses heperlinks to
allow easy navigation through topics.
Additional Enhancements:
Direct access to XPEDITER/Xchange
Display of CICS SYSID in all screen headings
Support for COBOL for OS/390 VM 2.1
Comatibility with IMS/ESA 6.1 and DB2 5.1
Support for not-object oriented COBOL extensions
10. Kanbay
Incorporate
Setting Breakpoints
Before
These are Unconditional breakpoints which will stop program execution before the
statement is executed.
Primary commands: Before , Bef, or B
Line commands: B
Examples:
Before 335 puts a breakpoint before line 335
Bef Get-time puts a breakpoint before the paragraph Get-
time
B All CICS Send puts a breakpoint before all CICS EXEC send
commands.
Optionally you can put a B on the line where you want a breakpoint before.
11. Kanbay
Incorporate
Setting Breakpoints
Before Conditional
These are same as Before breakpoints except it will only stop program execution if the condition is true
Primary commands: Before, Bef ,or B With IF statement.
Line commands: BC
Examples:
B Get-time if ws-applid EQ ‘ HITRGTB’ puts a conditional breakpoint
before the paragraph. Get time and
will only stop program execution if
the variable ws-applid is equal to
HITRGTB.
Conditions allowed are EQ, NE,GT,GE,LT, or LE Can use =,< >,>,>=,<,or <=signs.
Numeric variables can preceded or followed by a sign
Alphanumeric variables must be enclosed in either single or double quotes.
Hexadecimal variables must begin with an X followed by the string in either single or double quotes.
Optionally you can put a BC on the line where you want a breakpoint before, and you will be prompted to
enter a condition
12. Kanbay
Incorporate
Setting Breakpoints
After
These are unconditional breakpoints which will stop program execution after the
statement is executed.
Primary commands : After, Aft,or A
Line commands : A
Example:
After 335 puts a breakpoints after line 335
AFT Get-time puts a breakpoint after the paragraph
Get-time.
A All CICS Assign puts a breakpoint after all CICS EXEC
assign commands.
Optionally you can put a A on the line where you want a breakpoint before.
13. Kanbay
Incorporate
Setting Breakpoints
After Conditional
These are same as After breakpoints except it will only stop program execution if the
condition is true.
Primary commands: After, AFT, or with IF statement.
Example:
A Get-time if COUNT GT 10 puts a conditional breakpoint after the
paragraph Get-time and will only stop
execution when the statement counter is `
greater than 10. This is good for determining is your
program is looping.
Conditions allowed EQ,NE,GT,LT, or LE,or LE Can use =,<>,>,>=, < or <= signs.
Numeric variable can preceded or followed by a sign.
Alphanumeric variables must be enclosed in either singled or double quotes.
Hexadecimal variables must begin with an X followed by the string in either single
or double quotes.
Optionally you can put a AC on the line where you want a breakpoint after, and you
will be prompted to enter a condition.
14. Kanbay
Incorporate
Setting Breakpoints
When
These are conditional breakpoints based on change.
Primary commands: When or W.
Line commands: None
Examples:
When ws-applid EQ ‘HITRGTB’ stop program execution when the
variable ws-applid is equal to
HITRGTB.
When ws-applid CHANGES stop program execution when the
variable ws-applid changes.
Conditions allowed are EQ,NE,GT,GE,LT,or LE. Can use =,<>,>,>=,<,or<=
signs.
Numeric variables can preceded or followed by a sign.
Alphanumeric variables must be enclosed in either single or double quotes.
Hexadecimal variables must begin with an X followed by the string in either
single or double quotes.
15. Kanbay
Incorporate
Removing Breakpoints
There are three ways to remove a breakpoint:
1) Issue Before or After command using the OFF keyword
2) Use a line command
3) Using the DELETE command
Primary command: Delete, before, Bef,B,After,AFT,or A with IF statement.
Line commands: DA or DB
Examples:
After OFF 335 removes the breakpoint after line 335.
B OFF Get-time if ws-applid EQ-HITRGTB’ removes the conditional breakpoint before the
paragraph Get-time.
Delete WHENS ws-applid EQ ‘HITRGTB’ deletes the WHEN breakpoint.
Optionally you can put a DA or DB on the line where you want to remove the breakpoint from.
16. Kanbay
Incorporate
Breakpoint Rules
You can put a before and an after breakpoint on the same statement and/or paragraph
but only one can be conditional.
You can delete either the before or after breakpoint from one with both types of
breakpoint without affecting the other one.
The RELEASE command removes all breakpoints form a program.
The SHOW BREAKS command shows all the lines that have breakpoints set on.