CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

JSPs
The application uses three JSPs to format and display the results. One of three
scenarios can occur:
► The request completes successfully
► An error is reported in the ECIRequest object
► An exception occurs inside the CICS TG Java class library
348 CICS Transaction Gateway V5
results.jsp
The JSP results.jsp processes successful completion of a request. The JSP
defines the title of the HTML page and the style sheet used to format the HTML
in the header. The JSP defines the JavaBeans components that the page uses to
format and display the results (Figure B-11).
Figure B-11 JavaBeans components used by results.jsp
These components are all in the request scope and are all String objects. Their
IDs correspond to the names of the attributes we set in the HttpRequest in our
servlet. They contain the result of the CICS request made by the servlet.
The page then includes our common JSP header, which displays the information
specified in the initial form, such as Gateway daemon URL and user ID. The rest
of the page then outputs the values of the request attributes using the scriptlet
format , shown in Figure B-12. In our application, the
JavaBean component returnCode contains the ECI return code, and is inserted
into the HTML output with the JSP scriplet .
Return Codes
ECI return code:
ECI error msg:
Abend code:
Figure B-12 Outputting the results into the HTML