SMP/E receive via CSM failed with:
13.27.52 S0884738 IGD17001I DUPLICATE DATA SET NAME ON VOLUME SWK001 670
670 FOR DATA SET SYS22007.T132750.RA000.SPGHAT.R0105715
13.27.52 S0884738 IGD17001I DUPLICATE DATA SET NAME ON VOLUME SWK004 671
671 FOR DATA SET SYS22007.T132750.RA000.SPGHAT.R0105715
13.27.52 S0884738 IGD17001I DUPLICATE DATA SET NAME ON VOLUME SWK003 672
672 FOR DATA SET SYS22007.T132750.RA000.SPGHAT.R0105715
13.27.52 S0884738 IGD17001I DUPLICATE DATA SET NAME ON VOLUME SWK005 673
673 FOR DATA SET SYS22007.T132750.RA000.SPGHAT.R0105715
13.27.52 S0884738 IGD17001I DUPLICATE DATA SET NAME ON VOLUME SWK000 674
674 FOR DATA SET SYS22007.T132750.RA000.SPGHAT.R0105715
13.27.52 S0884738 IGD17001I DUPLICATE DATA SET NAME ON VOLUME SWK002 675
675 FOR DATA SET SYS22007.T132750.RA000.SPGHAT.R0105715
13.27.52 S0884738 IGD17273I ALLOCATION HAS FAILED FOR ALL VOLUMES SELECTED FOR DATA SET 676
676 SYS22007.T132750.RA000.SPGHAT.R0105715
13.27.52 S0884738 IGD17277I THERE ARE (32) CANDIDATE VOLUMES OF WHICH (6) ARE ENABLED OR QUIESCED
13.27.52 S0884738 IGD17290I THERE WERE 1 CANDIDATE STORAGE GROUPS OF WHICH THE FIRST 1 678
678 WERE ELIGIBLE FOR VOLUME SELECTION.
678 THE CANDIDATE STORAGE GROUPS WERE:SORTWORK
13.27.52 S0884738 IGD17279I 26 VOLUMES WERE REJECTED BECAUSE THEY WERE NOT ONLINE
13.27.52 S0884738 IGD17279I 26 VOLUMES WERE REJECTED BECAUSE THE UCB WAS NOT AVAILABLE
13.27.52 S0884738 IGD17279I 6 VOLUMES WERE REJECTED BECAUSE OF DUPLICATE DATA SET NAME (041C0416)
13.27.52 S0884738 IEC614I EXTEND FAILED - RC 000, DIAGNOSTIC INFORMATION IS (04034379) , 682
682 STEP1,......,SYS22007.T132750.RA000.SPGHAT.R0105715
13.27.52 S0884738 IEC032I E37-08,IFG0554P,SPGHAT,STEP1,SYSUT1,A1DD,SWK003,04034379, 683
683 SYS22007.T132750.RA000.SPGHAT.R0105715
683 ERROR DESCRIPTION: IEC032I
683 A multi-volume physical sequential data set was being written on DASD.
683 Space on next volume is needed. Either no space, or data set already
683 existed, or no space on the VTOC or VTOC index. See manual for more
683 detail.
Release : 6.0
Component : CSM Common Services
From the result of testing it looks like CSM has no control over the SYSUTn temp datasets. They are always allocated with the same dataset name format, for example SYS22007.T132750.RA000.* using CSM or with batch SMP/E. I tried specifying a volser on the SYSUT1 DDDEF in the global zone of the CSI and it was ignored by CSM and SMP/E.
The reason for this is that SMS has control over the allocation of these SYSUTn datasets. Can you check with your SMS admin to see if this is the case? I think you get these same allocation failure using SMP/E in batch to do the receive.
If SMS is not involved in your allocation failures this JCL assigns a volser to SYSUT1 and should help. If SMS is involved then this volser will be ignored.
//SMPGO EXEC PGM=GIMSMP,REGION=4096K,PARM='DATE=U'
//SMPCSI DD DSN=HLQ.CSI,DISP=OLD
//SMPHOLD DD DUMMY
//SMPCNTL DD DDNAME=SYSIN
//SMPPTFIN DD DUMMY
//*
//SYSIN DD *
SET BOUNDARY(GLOBAL).
UCLIN.
REP DDDEF(SYSUT1)
CYL SPACE(5,1) NEW DELETE VOLUME(XXXXXX).
.
ENDUCL.
//
Update HLQ.CSI and XXXXXX, run the JCL then try the receive in CSM.