INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Jobs

Writing to TS

Writing to TS

(OP)
I'm debugging an assembler program that is abending on a item error after a read ts.

The situation is complicated by the user not being able to reproduce the error on demand... happens some of the time.

Another issue is that no diagnostic tools are available (other than CEDF of course).

The code is part of a very large system that is perhaps nearly 30 years old. It has many macros that produce the exec cics statements. The one I am concerned about is the write ts that creates the ts items that are read on re-entry... it has a nohandle specified, and is dealing with aux... the vsam temp storage dataset.

I've been away from CICS applications work for a number of years, but do recall from those 'old days' that specifying 'aux' wasn't good, and of course the nohandle will ignore errors.

Does anyone have any thoughts that they'd like to share ?

RE: Writing to TS

The idea of specifying NOHANDLE is that you are supposed to check DFHRESP and sometimes DFHRESP2 afterwards and act accordingly. If it's not doing that, then perhaps a quick & dirty way would be to put in a check that will abend the transaction so you can get a dump out and see what's going on.

If he's doing a TS write to AUX then it's possible that the VSAM file is filling up - you could check the CICS stats to see if this is the case. From memory, there are things you can do to force TS to go to MAIN without changing the code via resource definitions

Quote (AP reference for 3.1):

AUXILIARY
specifies that the temporary storage queue is on a direct access storage device
in auxiliary storage. This is the default value for the first write.
This option is ignored:
* for an existing queue,
* if a TSMODEL resource definition with a matching prefix is installed in the
system.
but obviously this depends on how much stuff you write to TS and how much memory you have to spare...

Steve

"Every program can be reduced by one instruction, and every program has at least one bug. Therefore, any program can be reduced to one instruction which doesn't work." (Object::PerlDesignPatterns)

RE: Writing to TS

(OP)
Thanks for the reply Steve. Yes, I did look into it a bit further to see that indeed DFHRESP is being examined. I am getting a dump, but it's reformatted by ABEND-AID and the passage of years since I have last seen a CICS transaction dump is making it difficult.

Just got yanked off the project anyway -  

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Resources

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close