Remove BRODCAST= from the OUTDEF initialization statement

Description: In z/OS V2R1, JES2 ignores any specifications of the BRODCAST= parameter on the OUTDEF initialization statement. If a TSO user is not currently logged on, notify messages are now issued locally (processing as with BRODCAST=YES) instead of being routed to the member that submitted the job (processing as with BRODCAST=NO). You can no longer use BRODCAST= to specify which member issues TSO notify messages when a user is not logged on. BRODCAST= specifications continue to have no effect on message processing when the TSO user is logged on.

Element or feature:

z/OS JES2.

When change was introduced:

z/OS V2R1.

Applies to migration from:

z/OS V1R13 and z/OS V1R12.

Timing:

Before the first IPL of z/OS V2R1.

Is the migration action required?

No, but recommended to keep your initialization deck clean of outdated and obsolete specifications.

Target system hardware requirements:

None.

Target system software requirements:

None.

Other system (coexistence or fallback) requirements:

None.

Restrictions:

None.

System impacts:

None.

Related IBM Health Checker for z/OS check:

None.

Steps to take: Follow these steps:

Check the OUTDEF statement in the JES2 initialization deck for BRODCAST= specifications.
Remove BRODCAST= specifications from the OUTDEF statement. Any value that you provide on BRODCAST= will be ignored. The system will issue notify messages for a TSO user that is not logged on, on the member that requested the message. The message will be placed in the broadcast data set by TSO on that member.

Reference information: See the following information: