IEF425I TX67893 EXCEEDED SWADS SPACE P01
IEF040I SWADS I / O ERROR INTERPRETING JOB TX67893 P01
Because the SWADS data set is the IEFRDER DD statement in the INIT proc, you probably could specify an alternative SWADS data set size using the SPACE= parameter on the START command for the initiator, maybe something like:
s init.p1,space=(trk,300,,contig)
but I am curious about what size what too small, maybe I should bump up the SPACE parameter in the INIT proc so nobody gets that message during install. The default value, as I'm looking at it right now, is:
SPACE=(176,(2000),,CONTIG)
which allocates enough DASD space to hold 2000 176-byte records. Maybe you could try:
s init.p1,space=(176,(3000),,contig)
and if that doesn't work,
s init.p1,space=(176,(4000),,contig)
increasing the space by 1000 until it works?
COPY INDD=SMPACDS,OUTDD=SMPCDS
IEB167I FOLLOWING MEMBER(S) COPIED FROM INPUT DATA SET REFERENCED BY SMPACDS -
IEB154I <B3>.<F8>b<E7><D4> HAS BEEN SUCCESSFULLY COPIED
Not sure about the 2nd; is this what everyone gets?
Don't know about the specific values, but yes, the member names in the SMP CDS/ACDS are mostly unprintable. SMP4 "encodes" the member name to pack more information into the available bytes. Unlike JCL and TSO commands, the underlying BPAM code doesn't actually care about member names being valid printable characters, and SMP4 takes advantage of that.
--
