Endevor set up is similar to what Edward Marks have stated above, application team builds it outside of Endevor then add the WSBIND
Changes to Endevor to support this:
> Site Symbolics were used to include the HLQ of the directory
> &C1COMMENT set to allow lower case characters and is used in the processor to include the directory to write the wsbind.
> Base is a USS directory, Delta is an ELIB
> Type defined with source length of 32000 with compare from 1 to 1; USS RECFM ==>NL
> Generate Processor - CONWRITE to take the source and write to a TEMP file; ENUSSUTL utility to support the copy of Temp file to the staged directory/files
> MOVE processor - ENUSSUTL to copy from &C1SSTAGE to &C1STAGE directory/file
> Shipment destinations define the HOST and REMOTE directory
I hope this helps.
------------------------------
Software Engineer
Enterprise Technology
Fiserv
Ky, USA
------------------------------
Original Message:
Sent: 02-26-2020 03:11 AM
From: Edward Marks
Subject: managing WSDL in Endevor
Our engineers build their WSBINDs outside of Endevor, we've created a WSBIND type and they add them in and promote them as normal. It works just fine.
Original Message:
Sent: 02-25-2020 11:41 AM
From: Karin Persson
Subject: managing WSDL in Endevor
We would like to hear if someone is using Endevor for WSDL and how it works for you.
We would like to maintain WSDL, XSD and generate WSBIND files with Endevor and having a WSPARM file with parameters for the bind.
Our tools are IDz and Carma interface.
Even if you don't have exactly that set up it would be interesting to hear how you think it is working for you. And if you felt it was hard to get it to work.