Bulk Data Movement Guide

10.5
- 10.5.6
- 10.5.5
- 10.5.4
- 10.5.3
- 10.5.2
- 10.5.1
- 10.4.1
- 10.4.0 HotFix 1
- 10.4.0

Back Next

Rules for Reject File Naming on z/OS

On MVS, PowerExchange uses the following reject file naming rules:

If you do not specify a reject file value, PowerExchange writes the reject data to the following data set:

userid.jname.JOBnnnnn.PWXR.strategy.Tnnnnnnn

Where:

userid
is the user ID under which the job runs.

jname
is the job name.

JOB
nnnnn
is the job number.

strategy
is I (Insert), U (Update), D (Delete), or M (Mutated Update).

T
nnnnnnn
is a unique name of up to eight characters in length.

PowerExchange uses JOB
nnnnn
if the PowerExchange Listener or netport job runs as a batch job or uses STC
nnnnn
if the PowerExchange Listener or netport job runs as a started task.

Optionally, you can enter a data set prefix. PowerExchange generates a unique data set name that has the following format:

prefix.Jnnnn.PWXR.strategy.Tnnnnnnn

The prefix
qualifier can be up to 19 characters in length.

Reject File Naming Conventions

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal

0 COMMENTS

We’d like to hear from you! Log in to comment.

Rename Saved Search

Table of Contents

Bulk Data Movement Guide

Bulk Data Movement Guide

Rules for Reject File Naming on z/OS

Rules for Reject File Naming on z/OS