Return Code 256 in job WSTOMCCS

book

Article ID: 110066

calendar_today

Updated On:

Products

CA Endevor Software Change Manager (SCM) CA Endevor Software Change Manager - Natural Integration (SCM) CA Endevor Software Change Manager - ECLIPSE Plugin (SCM) CA Endevor Software Change Manager - Enterprise Workbench (SCM)

Issue/Introduction



Endevor R18.SPI12: Error in WSTOMCCS after apply of SO04386, everything looks OK  except the following error at the end of upgrade log, how to check if upgrade failed or not ? 

 ** Run-time validation
 >> Various run-time validations.
  > Submitting Validation job built from SYSES.DVP.ENDEVOR.R18SP0.INSTALL(NVTOMSTP):
   > Submitted Job =
   > Waiting for completion ...
   >  has timed out!
   > Please look at the output of the  to identify the reason of time out.

 

Environment

Release: ENDAE.00200-18-Endevor-Software Change Manager
Component:

Resolution

SO04386 is a post V18.0.12 PTF,  it only updates ENWSWAR and  ENWSWAR5

++HFS(ENWSWAR ) SYSLIB(CSIQUSS0) DISTLIB(ASIQHFS) 
BINARY 
LINK('../tpv/tomcat/shared/EndevorService.war') 
++IMBED ENWSWAR HFS 
++HFS(ENWSWAR5) SYSLIB(CSIQUSS0) DISTLIB(ASIQHFS) 
TEXT 
LINK('../tpv/tomcat/shared/EndevorService.war.md5'

The file size for EndevorService.war is 2623801. 

Customer can go to USS and check the time stamp and file size of  EndevorService.war  to verify if upgrade script runs OK. 

Also check upgrade script output, if there is no error except for a time out in the run-time validation, customer can submit WSTOMSTC manually, if there is no error in the WSTOMSCT sysout, that means upgrade is successful.