|
View previous topic :: View next topic
|
| Author |
Message |
John Poulakos
Active User
Joined: 13 Jun 2012
Posts: 178
Location: United States
|
|
|
|
Can anyone suggest a reason why a pipeline scan would fail to recognize one bind object? I have done many web service providers and have never run into this before. I created a new web service provider, it's a very simple program that performs some basic utility functions in CICS to reset a terminal... runs fine in test CICS. I installed the program and all definitions in prod CICS and put the wsdl and bind files in the appropriate Unix folders. Again, I have done this many times before.
For some reason, the pipeline scan is not picking up the new web service bind. The MSGUSER log shows the new web service was not found. It's in the same bind directory as all the other web services. Can anyone suggest something that might cause this? |
|
| Back to top |
|
 |
John Poulakos
Active User
Joined: 13 Jun 2012
Posts: 178
Location: United States
|
|
|
|
The pipeline scan command "cemt perform pipeline(provpipe) scan" scans the pipeline definition file (provpipe) for any wsbind files. The problem was I spelled wsbind wrong (wsbin) and you can't see the entire file name in our change management system. The only way to see it is in the Unix directory display under TSO, using PF4 key. But, first I had to get authorization to view the production Unix directory path.
CICS presents no indications of any errors, so it's hard to track down. |
|
| Back to top |
|
|
|
|
