JES2 output problem when migrating from OS/390 V2.10 to z/OS V1.4

JES2 output problem when migrating from OS/390 V2.10 to z/OS V1.4

We are migrating a system from OS/390 2.10 to z/OS 1.4. When z/OS is brought up, a HASP497 message is issued: rc=a8. HASP440 is issued next. The problem is that all JES2 destinations go to the node name and not the destination in the JES2 deck; it's almost like it thinks the output is destined for another system.

The sysplex name, SID, JES2 checkpoint, node name and so on are all the same on the 2.10 and 1.4 systems. No cold start was done on the JES2 spool. Do you think this would cause the destination issue? Would you recommend a cold start of JES2? Putting z/OS 1.4 on a test LPAR and a test JES2 spool does not duplicate this problem.

    Requires Free Membership to View

    Login

    When you register, you’ll also receive targeted alerts from my team of editorial writers and independent industry experts with the latest news, tips, and advice to help you do your job more efficiently and effectively. Our goal is to keep you informed on the hottest topics and biggest challenges faced by IT professionals today working with data center technologies.

    Margie Semilof, Editorial Director

    By submitting your registration information to SearchDataCenter.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchDataCenter.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

  1. Do you use any JES2 exits? If so, have you reassembled them? If your answers are yes and no, reassemble all your exits, because they all need to be reassembled with the new JES2 MACLIB when migrating from OS/390 V2.10 to z/OS V1.4. See the z/OS V1R4.0 Migration Guide for more details. It strikes me that this is a possibility, since field offsets have changed.

  2. I don't think you should have to do a cold start, but since an error in the output queue has been detected and rebuilt, it may be worth trying. Try to quiesce all work in the system, and flush or print or redirect as much output as possible prior to this to minimize lost output.

  3. If neither of the above options applies or helps, please get back to me with the full text of the messages, and I'll look into this further.

This was first published in December 2005

Back to top