Hi Jady,
I did some playing around with USS stuff in Endevor Processors and Symbolics. Yes, it can be done.
Here is the Generate Processor I set up:
//***************************************************************
//*
//DFHLS2WS PROC PROJECT='BST.ABEJU01.CNTL',
// USSABEJU=' '
//*
//***************************************************************
//* Step 1 - Copy the Java parameters to a HFS file
//***************************************************************
//*
//INPUT EXEC PGM=IEBGENER
//SYSPRINT DD DUMMY
//SYSUT1 DD DUMMY,DISP=SHR
//SYSUT1 DD *
PDSLIB=ENDEVOR.COPYBOOK
LANG=COBOL
PGMINT=CHANNEL
CONTID=DFHWS-DATA
MAPPING-LEVEL=1.2
URI=&C1COMMENT
LOGFILE=&USSABEJU..provider/&C1COMMENT..log
WSBIND=&USSABEJU..provider/&C1COMMENT..wsbind
WSDL=&USSABEJU..provider/&C1COMMENT..wsdl
// DD DISP=SHR,DSN=&PROJECT(&C1ELEMENT)
//SYSUT2 DD PATH='&USSABEJU..&C1COMMENT..in',
// PATHOPTS=(OWRONLY,OCREAT,OTRUNC),
// PATHMODE=SIRWXU,
// FILEDATA=TEXT,
// RECFM=VB,
// LRECL=137,
// BLKSIZE=32760
//SYSIN DD DUMMY
/*
//
In the Processor Group Symbolic definitions, for each stage, I have the appropriate override specified:
Stage 4 has:
SYMBOLIC -/O VALUE
PROJECT - BST.ABEJU01.CNTL
USSABEJU O &#USSABEJU#4
And then in the Site Symbolics, I have --
$ESYMBOL SYMNAME=#USSABEJU#1,SYMDATA='/a/abeju01/ENDVUSS/Dev'
$ESYMBOL SYMNAME=#USSABEJU#2,SYMDATA='/a/abeju01/ENDVUSS/QA'
$ESYMBOL SYMNAME=#USSABEJU#3,SYMDATA='/a/abeju01/ENDVUSS/EFix'
$ESYMBOL SYMNAME=#USSABEJU#4,SYMDATA='/a/abeju01/ENDVUSS/Prod'
So I build the first part of the HFS path with the Symbolics and the rest is done in the Processor.
It took a bit of experimenting to get thing working just right but it ended up working pretty nicely.
June