ATB013E

Explanation
 The system was unable to initialize Advanced Program-to-Program
Communication (APPC) because of a syntax error in one of the following
places:  The APPC keyword specified in the START APPC command
The subparameters specified in the PARM parameter of the EXEC
statement in the APPC member of SYS1.PROCLIB

System action
 The system continues processing without APPC.

Operator response
 Check the syntax of the APPC keyword value
specified in the START APPC command.  The value should be one of the
following:  A single two-character parmlib suffix
A list of parmlib suffixes separated by commas and optionally
ended by an L.  You must enclose the list in parentheses.

 See z/OS MVS System Commands for
the syntax of the START APPC command.

System programmer response
 In the APPC member of SYS1.PROCLIB,
check the syntax of the subparameters specified in the PARM parameter
of the EXEC statement that invokes the APPC initialization routine.
 The
syntax must follow these rules:  The required APPC subparameter must be a symbolic parameter corresponding
to the one in the PROC statement. For example, if the parameter in
the PROC statement is APPC=00, then the APPC subparameter should be
APPC=&APPC.
The optional BUFSTOR subparameter must be a 1- to 4-digit numeric
value. Examples are BUFSTOR=1024 or BUFSTOR=88.
The optional CONVBUFF subparameter must be a 1- to 7-digit numeric
value. Examples are CONVBUFF=1000 or the maximum value of CONVBUFF=2097152.
If you specify the APPC, BUFSTOR, and CONVBUFF subparameters (or
any two of those three subparameters), you can specify them in any
order, but you must separate each with a comma.
You cannot specify the APPC, BUFSTOR, or CONVBUFF parameter more
than once.

 For more information about the APPC initialization subparameters.
see the topic on
improving performance through system changes in z/OS MVS Planning: APPC/MVS Management. 

Module
 ATBINPR

Source
 APPC/MVS

Routing Code
 2

Descriptor Code
 5