Reviewing communications entries and remote location names

Ensure that the communications entries are secure.

When a communications job enters your system, the system uses the communications entries and the remote location name entries in the active subsystem to determine how the communications job will run. Look at this information in these entries:

All subsystems are capable of running communications jobs. If a subsystem that you intend for communications is not active, a job that is trying to enter your system might find an entry in another subsystem description that meets its needs. You need to look at the entries in all subsystem descriptions.
A communications entry contains a job description. The job description may contain request data that runs a command or program. Look at your communications entries and their associated job descriptions to ensure that you understand how jobs will start.
A communications entry also specifies a default user profile that the system uses in some situations. Make sure that you understand the role of default profiles. If your system contains default profiles, you should ensure that they are profiles with minimal authority.

You can use the Print Subsystem Description (PRTSBSDAUT) command to identify communications entries that specify a user profile name.

For additional information about the permissions assigned to default user profiles, see: Target system assignment of user profiles for jobs.