Rational Developer for System z

Step 5.4: Run the Generate Runtime Code wizard for each of the two generation properties files

In this step you will run the Generate Runtime Code wizard twice, first for the generation properties file for the invoked flow CheckItemAvailabilityGP.sfgen and then for the generation properties file for the top-level flow CatalogOrderGP.sfgen.

The Generate Runtime Code wizard gets input from the generation properties file that you specify, from the flow file referenced by the generation properties file, and from the many files and artifacts referenced by the flow file. The wizard generates as its output COBOL source code files, COBOL copy book files, JCL files, and other types of files (see Files created by the Generate Runtime Code wizard).

The wizard also has options to do the following tasks:

Most of these options will be used in this tutorial.

The Generate Runtime Code wizard always creates its output files in the same default directory that is used for storing new generation properties files (see Edit the generation properties file for CatalogOrder.seqflow).

However you can also specify a second location, either local (in your workspace) or remote (on a remote z/OS system), to which you want the wizard to copy the output files.

In this tutorial the output files are copied to a remote z/OS system.

Run the Generate Runtime Code wizard for CheckItemAvailabiltyGP.sfgen

In this subtopic you will run the Generate Runtime Code wizard using as input the generation properties file for the invoked flow, CheckItemAvailabiltyGP.sfgen.

To run the wizard for CheckItemAvailabiltyGP.sfgen:

  1. Start the Generate Runtime Code wizard:

    1. In the EST Project Explorer right-click CatalogSample > Generation > CICS SFR L2.0 > CheckItemAvailability > CheckItemAvailabiltyGP.sfgen.

    2. Click Generate > Generate Runtime Code.

    The Generate Runtime Code wizard opens.

  2. On the first page of the wizard, titled File selection:

    1. Set the File name field and the Generation target check box:
      Table 1. Set the values for File name and Generation target
      Field: Set the field to this value: Comment:
      File name: CheckItemAvailabilityGP.sfgen This field specifies the name of the generation properties file that is being used as input to the Generate Runtime Code wizard.
      Generate to another location Selected When this option is selected the wizard automatically copies the generated output files to a second destination, either local or remote, in addition to the default destination in a subfolder of the Generation folder.

      You specify the second destination to which these files are copied on the next page of the wizard.

    2. Set the options in the Job Control Information group:

      Table 2. Set the options in the Job Control Information group
      Field: Set the field to this value: Comment:
      Job Control user ID USER25 (example) This field specifies the user ID to be used with JCL commands in the generated JCL files.
      Job Control account USER25 (example) This field specifies the account name to be used with JCL commands in the generated JCL files.
      Deployment libraries HLQ USER25.ESTCA (example) This field specifies the high-level qualifier to be used with JCL commands in the generated JCL files.

      Specify the same high-level qualifier here that you used when you allocated data sets to contain the MVS files generated by the wizard (see Set up remote data sets to contain the generated MVS files).

      Do not add a trailing period.

      Create resource definitions JCL Cleared See the online help.
      Create compilation JCL Selected Selecting this check box causes the wizard to generate JCL files to compile the generated COBOL source files and copy books.
    3. Set the options in the Service Flow Systems Management group:

      Table 3. Set the options in the Service Flow Systems Management group
      Field: Set the field to this value: Comment:
      Have SFR manage creation of Program, Transaction, and ProcessType resources Cleared See the online help.
    4. Click Next.
      Note: The JCL Generation Warning window opens here if you have not modified or imported the JCL templates.

  3. On the second page of the wizard, titled Selection of target locations, you can specify an additional location, either local or remote, to which you want the Generate Runtime Code wizard to copy its output files (in addition to the default destination in a subfolder of the Generation folder).

    1. Select whether to copy the output files generated by the wizard to a local destination or to a remote destination:

      Table 4. Select the destination for copying the output files
      Field: Set the field to this value: Comment:
      • Generate to another local project

      • Generate to a remote location

      Generate to a remote location In this tutorial the output files created by the Generate Runtime Code wizard are copied to a remote z/OS system.
    2. Set the options in the z/OS UNIX locations group:
      Note: For the SFP file field you can set the value by: (a) typing a name; (b) dragging a directory from the Systems View pane; or (c) selecting a directory in the Systems View pane and clicking Add.
      Table 5. Set the options in the z/OS UNIX locations group
      Field: Set the field to this value: Comment:
      z/OS UNIX connection system.company (example) This field specifies the name of the Remote System connection (and therefore the remote z/OS system) that you want to use to select a z/OS UNIX System Services directory.
      SFP file /u/cicsts32/csfr/flowfiles (example) This field specifies the z/OS UNIX System Services directory into which the wizard is to copy the generated service flow properties file (see Service flow properties file).
    3. Set the options in the MVS locations group:
      Note: For the Source code, Copy members, and JCL fields:
      • Specify the same data sets that you created in the previous chapter (see Set up remote data sets to contain the generated MVS files).
      • You can set a value in one of these fields by: (a) typing a name; (b) dragging a data set from the Systems View pane; or (c) selecting a data set in the Systems View pane and clicking Add.

      Table 6. Set the options in the MVS locations group
      Field: Set the field to this value: Comment:
      MVS connection system.company (example) This field specifies the name of the Remote System connection (and therefore the remote z/OS system) that you want to use to select an MVS data set.
      Source code USER25.ESTCA.USER.SRCLIB (example) This field specifies the partitioned data set into which you want the wizard to copy the generated COBOL source files.
      Copy members USER25.ESTCA.USER.COPYLIB (example) This field specifies the partitioned data set into which you want the wizard to copy the generated copy book files.
      JCL USER25.ESTCA.USER.JCL (example) This field specifies the partitioned data set into which you want the wizard to copy the generated JCL files.
    4. Select Overwrite without prompt.

    5. Click Next.

  4. On the third page of the wizard, titled Compilation and Installation Options, you can specify compilation, build, and configuration actions that you want the wizard to perform on the remote z/OS system. These actions occur after the generated output files are copied to the remote z/OS system.

    1. Set the options for the JCL submission group:

      Table 7. Set the options in the JCL submission group
      Field: Set the field to this value: Comment:
      Submit compile JCLs Selected Selecting this check box causes the wizard to submit to z/OS the generated JCL files that compile the COBOL source files and copy books.
      Submit resource definition JCL Cleared See the online help.
    2. Set the options for the CICS Resource Definitions group:
      Note: If you have created one or more connections to a CICS primary connection region then:
      • The active connections are listed in the CICS System/Region list.
      • If you select the Request Pipeline Scan check box then the available pipelines are displayed in the list following the check box.
      Table 8. Set the options in the CICS Resource Definitions group
      Field: Set the field to this value: Comment:
      CICS System/Region NQA17C01 (example) This field lists the names of the active connections to the CICS primary connection regions.

      The connection that you defined earlier should be in this list (see Create a connection to a CICS Resource Definition server).

      Refresh You can click this button if you like. This button refreshes the following lists: (a) the list of connections in the CICS System/Region list; and (b) the list of active pipelines following the check box Request Pipeline Scans.
      Configure You can click this button if you like. This button opens the Connections page of the Preferences window, where you can create or modify connections to CICS primary connection regions.

      You have already created a connection of this type (see Create a connection to a CICS Resource Definition server).

      Install the Program, Transaction, and ProcessType resources Selected Select this check box if you want the wizard to install into CICS the Program, Transaction, and ProcessType resources for your program using the Application Deployment Manager.
      Rescan the Service Flow pickup directory Selected
      Note:

      You can clear this check box if you do not need this action performed.

      Examples:
      • a) In this tutorial you will select this same action when you generate runtime code for the main flow. Therefore you need not select the check box here.
      • b) If you were testing this flow separately, and were not generating code for the main flow yet, then you would need to select this check box here.
      Selecting this option causes the Generate Runtime Code wizard to request the CICS Service Flow Runtime to perform a scan of the service flow property pickup directory.

      The CICS Service Flow Runtime scans the service flow property pickup directory to detect and process any new SFP files in that directory.

      Request Pipeline Scans Selected
      Note:

      You can clear this check box if you do not need this action performed.

      See the examples in Rescan the Service Flow pickup directory.

      Selecting this option causes the Generate Runtime Code wizard to request the CICS Service Flow Runtime to perform a scan of the service flow property pickup directory.

      The CICS Service Flow Runtime scans the service flow property pickup directory to detect and process any new SFP files in that directory.

      List of pipelines Select the pipeline that you want the new Web service to use (for example, CICSSFRP) Selecting a pipeline causes the wizard to send a request to CICS to scan the pipeline.
      • Perform actions on Finish

      • Save CICS resource definitions to manifest file

      Perform actions on Finish Selecting this button causes the wizard to perform the actions that you have selected.

    3. Click Finish.

The Generate Runtime Code wizard creates the output files, copies the output files to the remote z/OS location, and performs any JCL file submissions or CICS configuration actions that have been specified.

After the wizard finishes its tasks it opens the Runtime Code Generation Complete window if all the operations were successful or it opens the Generation Error window if any errors have occurred. Either window contains a list of the actions that were attempted and whether they were performed successfully or failed.
Note: It is a good idea to copy and paste the contents of this list into another file in case you later decide that you want to examine the results further.

This window also lists messages for any errors or warnings that occurred. To find out more about a particular message displayed in this window:

  1. Select one of the items in the list.

  2. Press Ctrl-F1. A context-sensitive help window opens.

  3. In the help window select Error messages displayed by the Generate Runtime Code wizard. The online help for the Enterprise Service Tools error messages opens.

  4. In the online help for error messages there is a topic for each message. Each topic includes the error message code, the error message, an explanation of the message, and the user response you can perform to resolve the error.

Make a note of the job ID that was used to submit the JCL file (in Figure 1 the job ID is JOB25057.)

The output list should look like the following:

Figure 1. Output list for SAMPCIPN from the Runtime Generation Complete window
CRRZE7329W The Num Fields Descriptor in the Screen Description named
      Exmenu for screen EXMENU is not supported for Screen Recognition
      by this generator and, therefore, is ignored.
CRRZE7329W The Num Input Fields Descriptor in the Screen Description named
      Exmenu for screen EXMENU is not supported for Screen Recognition
      by this generator and, therefore, is ignored.
CRRZE7329W The Num Fields Descriptor in the Screen Description named
      Exinqc for screen EXINQC is not supported for Screen Recognition
      by this generator and, therefore, is ignored.
CRRZE7329W The Num Input Fields Descriptor in the Screen Description named
      Exinqc for screen EXINQC is not supported for Screen Recognition
      by this generator and, therefore, is ignored.
CRRZE7329W The Num Fields Descriptor in the Screen Description named
      EndPage for screen ENDPAGE is not supported for Screen Recognition
      by this generator and, therefore, is ignored.
CRRZE7329W The Num Input Fields Descriptor in the Screen Description named
      EndPage for screen ENDPAGE is not supported for Screen Recognition
      by this generator and, therefore, is ignored.
CRRZE7329W The Num Fields Descriptor in the Screen Description named
      Exmenu for screen EXMENU is not supported for Screen Recognition
      by this generator and, therefore, is ignored.
CRRZE7329W The Num Input Fields Descriptor in the Screen Description
      named Exmenu for screen EXMENU is not supported for Screen Recognition
      by this generator and, therefore, is ignored.
CRRZE7329W The Num Fields Descriptor in the Screen Description
      named Exinqc for screen EXINQC is not supported for Screen Recognition
      by this generator and, therefore, is ignored.
CRRZE7329W The Num Input Fields Descriptor in the Screen Description
      named Exinqc for screen EXINQC is not supported for Screen Recognition
      by this generator and, therefore, is ignored.
CRRZE7329W The Num Fields Descriptor in the Screen Description named
      EndPage for screen ENDPAGE is not supported for Screen Recognition
      by this generator and, therefore, is ignored.
CRRZE7329W The Num Input Fields Descriptor in the Screen Description named
      EndPage for screen ENDPAGE is not supported for Screen Recognition
      by this generator and, therefore, is ignored.
CRRZE7329W The Num Fields Descriptor in the Screen Description named
      Exinqc for screen EXINQC is not supported for Screen Recognition
      by this generator and, therefore, is ignored.
CRRZE7329W The Num Input Fields Descriptor in the Screen Description named
      Exinqc for screen EXINQC is not supported for Screen Recognition
      by this generator and, therefore, is ignored.
File 'SAMPCIPN.cbl' was created in 'CICS SFR L2.0/CheckItemAvailability'.
File 'EXINQC.CPY' was created in 'CICS SFR L2.0/CheckItemAvailability'.
File 'ENDPAGE.CPY' was created in 'CICS SFR L2.0/CheckItemAvailability'.
File 'VCHECKIT.CPY' was created in 'CICS SFR L2.0/CheckItemAvailability'.
File 'ICHECKIT.CPY' was created in 'CICS SFR L2.0/CheckItemAvailability'.
File 'EXMENU.CPY' was created in 'CICS SFR L2.0/CheckItemAvailability'.
File 'OCHECKIT.CPY' was created in 'CICS SFR L2.0/CheckItemAvailability'.
File 'SAMPCIPN.jcl' was created in 'CICS SFR L2.0/CheckItemAvailability'.
File 'SAMPCIRN.sfp' was created in 'CICS SFR L2.0/CheckItemAvailability'.
File 'SAMPCIPN' was created in 'USER25.ESTCA.USER.SRCLIB (mvs040)'.
File 'EXINQC' was created in 'USER25.ESTCA.USER.COPYLIB (mvs040)'.
File 'ENDPAGE' was created in 'USER25.ESTCA.USER.COPYLIB (mvs040)'.
File 'VCHECKIT' was created in 'USER25.ESTCA.USER.COPYLIB (mvs040)'.
File 'ICHECKIT' was created in 'USER25.ESTCA.USER.COPYLIB (mvs040)'.
File 'EXMENU' was created in 'USER25.ESTCA.USER.COPYLIB (mvs040)'.
File 'OCHECKIT' was created in 'USER25.ESTCA.USER.COPYLIB (mvs040)'.
File 'SAMPCIPN' was created in 'USER25.ESTCA.USER.JCL (mvs040)'.
File 'SAMPCIRN.sfp' was created in '/u/cicsts32/csfr/flowfiles (mvs040)'.
JCL file SAMPCIPN.jcl was submitted as job JOB25057 to host mvs040
A request to scan pipeline CICSSFRP was successfully submitted.
Program SAMPCIPN was successfully created on CICS System/Region NQA17C01.
Transaction SADI was successfully created on CICS System/Region NQA17C01.
Processtype SAMPCIRN was successfully created on host NQA17C01.
Service Flow pickup directory successfully scanned.
Note:
  • You can ignore the warning message CRRZE7329W, which indicates that a particular type of descriptor is not supported current runtime. Because the Generate Runtime Code wizard skips this descriptor without processing it, the generated output files are not affected.
  • If an error message indicates that the CICS Resource Definition (CRD) server encountered a problem then follow the instructions in the User response section of topic CRRZE7206E.

Check for JCL errors and compile and link errors

In the Remote Systems view, expand the JES node, find your job, and check the output files generated for the JCL file that you submitted.

There should not be any JCL error messages or compile or link error messages other than informational messages (see Step 5.6: Troubleshooting).

Run the Generate Runtime Code wizard for CatalogOrderGP.sfgen

In this subtopic you will run the Generate Runtime Code wizard using as input the generation properties file for the top-level flow CatalogOrderGP.sfgen.

To run the wizard on CatalogOrderGP.sfgen:

  1. Start the Generate Runtime Code wizard:

    1. In the EST Project Explorer expand CatalogSample > Generation > CICS SFR L2.0 > CatalogOrder.

    2. Right-click CatalogOrderGP.sfgen.

    3. Select Generate > Generate Runtime Code.

    The Generate Runtime Code wizard opens.

  2. On the first page of the wizard, titled File selection, you provide primary information:

    1. Set the File name field and the Generation target check box:
      Table 9. Set the file name and generation target
      Field: Set the field to this value: Comment:
      File name: CatalogOrder.sfgen This field specifies the name of the generation properties file that is being used as input to the Generate Runtime Code wizard.
      Generate to another location Selected When this option is selected the wizard automatically copies the generated output files to a second destination, either local or remote, in addition to the default destination in a subfolder of the Generation folder.

      You specify the second destination to which these files are copied on the next page of the wizard.

    2. Set the options in the Job Control Information group:

      Table 10. Set the options in the Job Control Information group
      Field: Set the field to this value: Comment:
      Job Control user ID USER25 (example) This field specifies the user ID to be used with JCL commands in the generated JCL files.
      Job Control account USER25 (example) This field specifies the account name to be used with JCL commands in the generated JCL files.
      Deployment libraries HLQ USER25.ESTCO (example) This field specifies the high-level qualifier to be used with JCL commands in the generated JCL files.

      Specify the same high-level qualifier here that you used when you allocated data sets to contain the MVS files generated by the wizard (see Set up remote data sets to contain the generated MVS files).

      Do not add a trailing period.

      Create resource definitions JCL Cleared See the online help.
      Create compilation JCL Selected Selecting this check box causes the wizard to generate JCL files to compile the generated COBOL source files and copy books.
    3. Set the options in the Service Flow Systems Management group:

      Table 11. Set the options in the Service Flow Systems Management group
      Field: Set the field to this value: Comment:
      Have SFR manage creation of Program, Transaction, and ProcessType resources Cleared See the online help.
    4. Click Next.
      Note: The JCL Generation Warning window opens here if you have not modified or imported the JCL templates.

  3. On the second page of the wizard, titled Selection of target locations, you can specify an additional location, either local or remote, to which you want the Generate Runtime Code wizard to copy its output files (in addition to the default destination in a subfolder of the Generation folder).

    1. Select whether to copy the output files generated by the wizard to a local destination or to a remote destination:

      Table 12. Select a local or remote destination for copying files
      Field: Set the field to this value: Comment:
      • Generate to another local project

      • Generate to a remote location

      Generate to a remote location In this tutorial the output files created by the Generate Runtime Code wizard are copied to a remote z/OS system.
    2. Set the options in the z/OS UNIX locations group:
      Note: For the WSBind file field, the WSDL file field, and the SFP file field, you can set the value by: (a) typing a name; (b) dragging a directory from the Systems View pane; or (c) selecting a directory in the Systems View pane and clicking Add.
      Table 13. Set the options in the z/OS UNIX locations group
      Field: Set the field to this value: Comment:
      z/OS UNIX connection system.company (example) This field specifies the name of the Remote System connection (and therefore the remote z/OS system) that you want to use to select a z/OS UNIX System Services directory.
      WSBind file /u/cicsts32/webservices/wsbind/cicssfrp (example) Specify the z/OS UNIX System Services directory into which you want the wizard to copy the generated WSBind file.

      If you have configured a CICS system definition using the CICS resource definition editor and if a query from the CICS system definition to the remote CICS region is successful then this field is a list of remote directories from which you can select.

      WSDL file /u/cicsts32/webservices/wsbind/cicssfrp (example) Specify the z/OS UNIX System Services directory into which you want the wizard to copy the generated WSDL file.

      If you have configured a CICS system definition using the CICS resource definition editor and if a query from the CICS system definition to the remote CICS region is successful then this field is a list of remote directories from which you can select.

      SFP file /u/cicsts32/csfr/flowfiles (example) This field specifies the z/OS UNIX System Services directory into which the wizard is to copy the generated service flow properties file (see Service flow properties file).
    3. Set the options in the MVS locations group:
      Note: For the Source code, Copy members, and JCL fields:
      • Specify the same data sets that you created in the previous chapter (see Set up remote data sets to contain the generated MVS files).
      • You can set a value in one of these fields by: (a) typing a name; (b) dragging a data set from the Systems View pane; or (c) selecting a data set in the Systems View pane and clicking Add.

      Table 14. Set the options in the MVS locations group
      Field: Set the field to this value: Comment:
      MVS connection system.company (example) This field specifies the name of the Remote System connection (and therefore the remote z/OS system) that you want to use to select an MVS data set.
      Source code USER25.ESTCO.USER.SRCLIB (example) This field specifies the partitioned data set into which you want the wizard to copy the generated COBOL source files.
      Copy members USER25.ESTCO.USER.COPYLIB (example) This field specifies the partitioned data set into which you want the wizard to copy the generated copy book files.
      JCL USER25.ESTCO.USER.JCL (example) This field specifies the partitioned data set into which you want the wizard to copy the generated JCL files.
    4. Select Overwrite without prompt.

    5. Click Next.

  4. On the third page of the wizard, titled Compilation and Installation Options, you can specify compilation, build, and configuration actions that you want the wizard to perform on the remote z/OS system. These actions occur after the generated output files are copied to the remote z/OS system.

    1. Set the options for the JCL submission group:

      Table 15. Set the options in the JCL submission group
      Field: Set the field to this value: Comment:
      Submit compile JCLs Selected Selecting this check box causes the wizard to submit to z/OS the generated JCL files that compile the COBOL source files and copy books.
      Submit resource definition JCL Cleared See the online help.
    2. Set the options for the CICS Resource Definitions group:
      Note: If you have created one or more connections to a CICS primary connection region then:
      • The active connections are listed in the CICS System/Region list.
      • If you select the Request Pipeline Scan check box then the available pipelines are displayed in the list following the check box.
      Table 16. Set the options in the CICS Resource Definitions group
      Field: Set the field to this value: Comment:
      CICS System/Region system.company (example) This field lists the names of the active connections to the CICS primary connection regions.

      The connection that you defined earlier should be in this list (see Create a connection to a CICS Resource Definition server).

      Refresh You can click this button if you like. This button refreshes the following lists: (a) the list of connections in the CICS System/Region list; and (b) the list of active pipelines following the check box Request Pipeline Scans.
      Configure You can click this button if you like. This button opens the Connections page of the Preferences window where you can create or modify connections to CICS primary connection regions.

      You have already created a connection of this type (see Create a connection to a CICS Resource Definition server).

      Install the Program, Transaction, and ProcessType resources Selected Select this check box if you want the wizard to install into CICS the Program, Transaction, and ProcessType resources for your program using the Application Deployment Manager.
      Rescan the Service Flow pickup directory Selected Selecting this check box causes the Generate Runtime Code wizard to request the CICS Service Flow Runtime to perform a scan of the service flow property pickup directory.

      The CICS Service Flow Runtime scans the service flow property pickup directory to detect and process any new SFP files in that directory.

      Request Pipeline Scans Selected Selecting this check box causes the wizard to initiate a scan on a CICS pipeline.

      You can have one or more pipelines scanned by selecting the appropriate cells in the Scan column.

      List of pipelines Select the pipeline that you want the new Web service to use (for example, CICSSFRP) Selecting a pipeline causes the wizard to send a request to CICS to scan the pipeline.
      Perform actions on Finish Selected Clicking this button causes the wizard to perform the actions that you have selected.
      Save CICS resource definitions to manifest file Cleared See Step B8. The Compilation and Installation Options page of the Generate Runtime Code wizard.

    3. Click Finish.

The Generate Runtime Code wizard creates the output files, copies the output files to the remote z/OS location, and performs any JCL file submissions or CICS configuration actions that have been specified.

After the wizard finishes its tasks it opens the Runtime Code Generation Complete window if all the operations were successful or it opens the Generation Error window if any errors occurred. Either window contains a list of the actions that were attempted and whether they were performed successfully or failed.
Note: It is a good idea to copy and paste the contents of this list into another file, in case you later decide that you want to examine the results further.

This window also lists messages for any errors or warnings that occurred. To find out more about a particular message displayed in this window:

  1. Select one of the items in the list.

  2. Press Ctrl-F1. A context-sensitive help window opens.

  3. In the help window, click Error messages displayed by the Generate Runtime Code wizard. The online help for the Enterprise Service Tools error messages opens.

  4. In the online help for error messages there is a topic for each message. Each topic includes the error message code, the error message, an explanation of the message, and the user response you can perform to resolve the error.

Make a note of the job ID that was used to submit the JCL file (in Figure 2 the job ID is JOB25051.)

The output list should look like the following:

Figure 2. Output list for SAMPCAPN from the Runtime Generation Complete window
File 'SAMPCAPN.cbl' was created in 'CICS SFR L2.0/CatalogOrder'.
File 'DFH0XCMN.CPY' was created in 'CICS SFR L2.0/CatalogOrder'.
File 'VCATALOG.CPY' was created in 'CICS SFR L2.0/CatalogOrder'.
File 'ICHECKIT.CPY' was created in 'CICS SFR L2.0/CatalogOrder'.
File 'ICATALOG.CPY' was created in 'CICS SFR L2.0/CatalogOrder'.
File 'OCHECKIT.CPY' was created in 'CICS SFR L2.0/CatalogOrder'.
File 'OCATALOG.CPY' was created in 'CICS SFR L2.0/CatalogOrder'.
File 'SAMPCAPN.jcl' was created in 'CICS SFR L2.0/CatalogOrder'.
File 'sampcapn.wsbind' was created in 'CICS SFR L2.0/CatalogOrder'.
File 'sampcapn.wsdl' was created in 'CICS SFR L2.0/CatalogOrder'.
File 'SAMPCARN.sfp' was created in 'CICS SFR L2.0/CatalogOrder'.
File 'SAMPCAPN' was created in 'USER25.ESTCO.USER.SRCLIB (mvs040)'.
File 'DFH0XCMN' was created in 'USER25.ESTCO.USER.COPYLIB (mvs040)'.
File 'VCATALOG' was created in 'USER25.ESTCO.USER.COPYLIB (mvs040)'.
File 'ICHECKIT' was created in 'USER25.ESTCO.USER.COPYLIB (mvs040)'.
File 'ICATALOG' was created in 'USER25.ESTCO.USER.COPYLIB (mvs040)'.
File 'OCHECKIT' was created in 'USER25.ESTCO.USER.COPYLIB (mvs040)'.
File 'OCATALOG' was created in 'USER25.ESTCO.USER.COPYLIB (mvs040)'.
File 'SAMPCAPN' was created in 'USER25.ESTCO.USER.JCL (mvs040)'.
File 'sampcapn.wsbind' was created in
      '/u/cicsts32/webservices/wsbind/cicssfrp (mvs040)'.
File 'sampcapn.wsdl' was created in
      '/u/cicsts32/webservices/wsbind/cicssfrp (mvs040)'.
File 'SAMPCARN.sfp' was created in
      '/u/cicsts32/csfr/flowfiles (mvs040)'.
JCL file SAMPCAPN.jcl was submitted as job JOB25051 to host mvs040
A request to scan pipeline CICSSFRP was successfully submitted.
Program SAMPCAPN was successfully created on CICS System/Region
      NQA17C01.
Transaction SADP was successfully created on CICS System/Region
      NQA17C01.
Processtype SAMPCARN was successfully created on host NQA17C01.
Service Flow pickup directory successfully scanned.
Note:
  • If an error message indicates that the CICS Resource Definition (CRD) server encountered a problem then follow the instructions in the User response section of topic CRRZE7206E.

Check for JCL errors and compile and link errors

In the Remote Systems view, expand the JES node, find your job, and check the output files generated for the JCL file that you submitted.

There should not be any JCL error messages or compile or link error messages other than informational messages (see Step 5.6: Troubleshooting).


Feedback