v5r1m0 spool file change

In V5R1 the maximum number of spool files per job has increased from
9999 to 999999.  This change does not impact the various spool APIs as
the APIs used a Binary(4) to hold the spool number --  which can
easily handle these increased values.

Other interfaces however are impacted (outfiles which returned spool
number as a zoned decimal 4,0 value; *MSGD which returned spool number
as a Binary(2); etc.) and so system value QMAXSPLF was introduced so
that these interfaces could continue to be used.  These interfaces
were also enhanced to return new elements (outfile zoned 6,0; *MSGD
Binary(4); etc.), in addition to the previous elements, so that
applications can start using the larger values with hopefully minimal
changes being required.

Your reference to 32767 is probably the limit associated with what
value can be returned in a signed Binary(2); and is not the new system
limit.

Bruce

>
>We're upgrading from v4r5 v5r1 this weekend or next and I'm reading the Memo
>to Users.  It appears that the maximum number of spool files allowed per job
>has increased from 9999 to 32767.  Can anyone confirm this?  Also, how has
>this affected API's which use the spool file number?
>