Jazz Set Up

Jazz Set Up. 1

PREREQUISITES. 2

Step 1: Download Jazz and Supporting Objects. 2

Optional Step: Install Training Materials. 6

Step 2.  Initial Jazz test 6

Step 3.  Generate COBOL: the Lang Tab. 7

z/OS Set Up. 10

Set up: the z/OS tab. 11

Processing. 13

Test a COBOL Compile. 14

Edit JZL Templates. 14

Compile Support Subprograms. 15

Validate remaining templates. 18

Set Up Jazz to work with Micro Focus and an IDE.. 19

Appendices. 19

Jazz Extensions. 19

Various Issues. 20

Trouble-Shooting Installation. 20

Glossary. 22

 

This Help page tells you how to install and configure Jazz so that you can run it as in the examples shown in the videos.  

Click here to see these set-up instructions as a video.  Note: this document will be updated first: the video may show an earlier Jazz release.

To run Jazz your organisation will have arranged for a licence that permits you and others to download and run Jazz from the Jazz Software web site, and your Jazz administrator will have given you a password with which to log on to the Jazz web site.  Use your email plus this password to log on.  


Log on, then click the button [Run Jazz].  This downloads a copy of Jazz to your computer, installs it, and puts an icon on your desktop to run it again.  You can save the Jazz icon on your desktop or taskbar and continue running it by clicking this icon.  This diagram shows what will happen: -

When you run Jazz from the icon: -

1.      If you are connected to the Internet then Jazz will check with the website to see if there is a later version, and down load this if necessary.

2.      If you are not connected to the Internet then Jazz will run anyway for about a month.  However if it is longer than this then you need to go online again to refresh your licence, and to check that you have the latest version.

3.      Of course running Jazz from the [Run Jazz] button is like running Jazz from the icon while you’re on line.

PREREQUISITES.  

1.      Jazz requires a Windows computer with an Internet connection.  Tests have verified that it can be installed into Windows-XP, Windows-7, and Windows-10, and Windows environments on a Macintosh or Linux computer.  This computer might be a stand-alone computer or laptop, or be part of a LAN.

2.      To install Jazz the software is downloaded from the Internet using Microsoft ClickOnce technology.  This installs the software into a “sandbox” where it does not interfere with any other programs.  The install will also install the correct version of the .Net framework if it is not already installed.  This framework will already be present with Windows-7 or later.

3.      The browser that you use to install Jazz must have the Microsoft Clickonce extensions installed.  This is standard with Internet Explorer and Edge, but with Firefox, Chrome, etc you may need to install an AddIn. Google xxxx ClickOnce (e.g. “Chrome ClickOnce”). If you have problems (see Trouble-Shooting Installation) try installing Jazz with Internet Explorer or Edge: you do not have to make them your default browser: once installed Jazz will run from the Jazz icon whether or not your default browser supports ClickOnce.

4.      You will need access to a z/OS environment where you can compile and test your programs.  This may be a real IBM mainframe (I’ve used the IBM Dallas Test Centre), or a simulated mainframe such as the Micro Focus Mainframe Subsystem.  You may set Jazz up to work with either or both environments.

Step 1: Download Jazz and Supporting Objects

The first time that you run Jazz you will need to set it up.

1.      First, decide where you will store your Jazz programs.  If you’re working on your own this will probably be within your “My Documents” folder.  If there are several members of your project team who will be using Jazz this should be on a common server and the reference to it should be the same for each of you, so that you can share various project files.

2.      Start up Jazz by opening the JazzSoftware web page with a Microsoft Browser (Internet Explorer or Edge) or another browser with ClickOnce Add-in enabled and clicking the button [Run Jazz]. This will download a copy of Jazz into a temporary folder, check for pre-requisites (ASP.NET 4.0) and download them if necessary, and then start running Jazz.  See Trouble-Shooting Installation if Jazz doesn’t start.  You may see a screen like this: -


Click [Install] and this screen will appear as Jazz is installed: -

 

3.      Define Windows Folders

Jazz then starts up, and immediately discovers that it is not configured correctly so instead of starting the Jazz Workbench it opens the Configuration form: -

To run Jazz you will need a folder that your Windows computer can access where Jazz can save objects – programs, copy books, and so on – for your project.  This may be on your own computer, or be on a shared LAN drive. 

If you are using Jazz with Micro Focus and an IDE such as Visual Studio or Eclipse, set the IDE combo box.  Otherwise leave it at the default setting of None.  If you’re using Micro Focus with Visual Studio create a VS project with type Mainframe Subsystem Application.  Eclipse hasn’t yet been developed: in the meantime follow the directions for Visual Studio and let us know of any problems.

If this is your very first set-up Jazz should now automatically start checking the folder locations.  Common folder, which has a default value of “*”, will turn yellow and a dialog box will appear for you to locate or create the common folder.  If this doesn’t happen automatically (as when you’re starting a new project, but you’ve used Jazz before), click [Check Paths].

The Jazz Common Path folder is the folder that contains one or several of your projects.   Click [Locate] and you can browse to the folder you want, or create a new one. 

  • With IDE = None and a personal project, this will probably be your My Documents folder, for example mine was
                C:\Users\Advanced Computers\Documents. 
    With a shared project this will be on a shared LAN drive.
  • With IDE = Visual Studio or Eclipse, this will be the folder where the IDE creates projects.  For example, using Micro Focus Enterprise Developer with VS2017, this will be the folder were you create your COBOL projects, e.g. mine was
                 C:\tutorials

Next, define the project folder.  This will be a folder within the common path, and the Microsoft Browse for Folder dialog opens on it.  For None, locate or create a suitable folder. If you’re using an IDE (Visual Studio, Eclipse) choose the project that you created earlier.

Jazz then checks that the project contains the required subfolders.   You can leave the subfolder name blank, in which case Jazz will save the corresponding objects directly into the project folder, and subfolders may all have the same name.  Different object types can be distinguished by their extension, so it’s simply a personal preference whether you have 0 to 4 subfolders.   Any missing subfolder initiates a locate/create dialog as above.

If we are creating new subfolders we’ll probably just click [Create] to create a subfolder of that name, although we might use [Locate] to choose another subfolder within the common folder. 

NB: although Microsoft’s Browse for Folder dialog will let you navigate to a folder anywhere on your Windows system, Jazz requires that the subfolders be directly within the project.  There will be error messages if you select a folder anywhere else.

4.      Initialise the Jazz Folders. 

When the folders are created then Jazz will copy a number of standard objects – Jazz programs etc. – into the folders.  If your Jazz folders are shared with other users then these will already exist, and you’ll get messages like this whenever Jazz finds a object already present: -

You’ll probably click [Ignore] or [Ignore All].  [Replace] or [Replace All] may replace objects which have been locally customised: check with your Jazz Site Admin.

Optional Step: Install Training Materials

If you are new to Jazz you may want to click [Add Training] to download various objects designed for an on-line tutorial.   This functions like Initialise Project above, adding objects to your Jazz Programs and Copy Code folders.  You may have created a special training project for this, avoiding unnecessary clutter in your normal projects.

Step 2.  Initial Jazz test

Following Step 1 Jazz will display the Jazz Workbench.   At this stage we run a very basic Jazz test to prove that we’ve configured it correctly so far: -

1.      Click the menu File/Open in the Jazz Workbench.  Select member PFirst, a little nonsense program: -

Jazz has analysed your program, colouring keywords and references, indenting statements to show logic, and reporting errors.  If you were to look at PFirst.jzz with Notepad it would look like this: -

*# Last Updated by IBMUSER at 5/06/2017 9:26:29 a.m.

PROGRAM PFirst;

COPY PFirstR;

PROCESS PFirstR WHERE (PFirstR.Field1 = 'X' | PFirstR.Field1 = 'Y');

PRINT (PFirstR.*);

END PROCESS PFirstR;

1.1.   With PFirst displayed in the workbench as above, right-click “Program”.   A web page will open telling you the rules of the PROGRAM statement.  This shows you that Help is working correctly.

1.2.   Change the program to introduce an error: for example changing “Program” to “Prgrm”.  Click [Check].  Jazz will react to the error with a number of error messages.  Right-click one of these errors: this will give you information about the error and how to correct it.

1.3.   Click the Help menu item.  You will see some Help Options: -

Explore these options to see what’s available under each option.  Other than About, the options open Help pages from the Jazz web site.

DON’T click [PROCESS] to compile and run the program!  We have more configuration steps to complete first.

Step 3.  Generate COBOL: the Lang Tab.

Click the Lang tab: - 

If your test environment is not IDE but z/OS the sections COBOL Copy Books and BMS Maps won’t appear.

Important options that you need to check: -

·         Cobol Dialect.   Either

o        Enterprise COBOL for z/OS to generate programs for either a z/OS mainframe, or the Micro Focus Mainframe Subsystem. 

o        Microsoft COBOL if you want to generate programs to run in a Windows or UNIX environment.

·         Test Environment.  Either

o        z/OS if your programs are going to be compiled and tested with a z/OS system, data being uploaded and downloaded with FTPS (File Transfer Protocol (Secure)

o        IDE if your programs are going to tested with an IDE (Visual Studio or Eclipse)

Other COBOL options that you may want to change from time to time: -

a.                  Include Jazz Program as Comments.  Almost certainly you’ll leave this checked, as its only cost is a few extra comment lines in the COBOL ENVIRONMENT division.

b.                  Show dictionary entries in Jazz Program.  Leave this unchecked: the extra comments are not useful at this stage.  This is included for future development

c.                  Sequence numbers (Left).  If unchecked, columns 1 to 6 of each line will be left blank.  If checked, then they will contain a sequence number which will increment by the amount given in the textbox.

d.                  Program Name from Col 72.  If checked the program name will be put in columns 73 to 80 of each line.  This may be useful to show the right-hand margin of the COBOL source code.

e.                  Create Diagnostic Code.  With this checked Jazz will generate statements to help with debugging in the event of error: you’ll usually be able to sort out what’s gone wrong from Jazz, without having to drill down to the level of COBOL.  There is a slight cost to this, so you may choose to uncheck this to generate slightly smaller and more efficient programs. 

f.                    STXIT Limit (Batch Only).  In batch programs Jazz may include a call to an Assembler routine, JZSTXIT to trap abends such as Data Exception, producing diagnostics relating the error to a Jazz statement and displaying some important information such as the current record.  If the limit is > 0 the program will then attempt to restart at the next record.  The textbox may be set to a value from 0 to 9.  If it is 0, or there have been too many abends then the default COBOL action, producing a dump, occurs.

This option is irrelevant if “Create Diagnostic Code” is unchecked, or Test Environment is IDE: in such cases Jazz does not include a call to JZSTXIT.

g.                  Max Jazz Error level.  As Jazz processes your programs it will produce message when it detects conditions that are, or might be, errors.  Error severity may be

·                     T          Terminal error:  Jazz can’t continue

·                     S          Severe Error:  Jazz can’t generate a correct COBOL program

·                     E          Error:  Jazz has made a correction that might result in a correct COBOL program

·                     W         Warning: Jazz has detected a condition that might be an error.  The program is probably correct

·                     I           Information:  This isn’t a problem, just something that Jazz thought you should know.

On the Language tab you can choose one of a maximum level: if Jazz reports errors of this severity level or greater then it won’t generate any COBOL.  Occasionally you might want to change this from “E” to “S” to allow Jazz to generate some COBOL anyway, you won’t want to allow Terminal errors, nor will you want to disallow Warnings or Information

CICS Options

a.                  CICS Mapping Level.  Set this to 3 or 4 depending on your CICS mapping level. The CICS Mapping Level affects the format of web service messages that have variable repeating sections: with 4 or greater Jazz will generate COBOL definitions with OCCURS nn DEPENDING ON xxx so that varying-length messages are handled.  With less than 4 full-length messages are transmitted even if only a few occurrences are actually present.

b.                  3270 Screen Template.  If you create your own standard 3270 screen template, then put its name here. 

 

COBOL Copy Books and BMS Maps

With Test Environment = IDE, these controls appear: -

Set them as here and click [Check Folders].  Create the folders as necessary.

If your test environment is z/OS then these folders are not necessary as libraries which are defined in the z/OS tab are used

With the Lang tab set up, we’re now ready to generate COBOL.  If we stop here then we could use Jazz to create COBOL programs but we would have to manually invoke our test system, submitting the COBOL and relevant JCL, when we want the programs to be compiled and run.

The next section deals with setting up our system to use a z/OS system, such as the IBM Dallas Test Centre, directly.  If we’re using an IDE then skip this section, instead go to Set Up Jazz to work with Micro Focus and an IDE

z/OS Set Up

We have completed basic set up, and Jazz is now able to check your program and (if it’s valid) generate COBOL.  This section is only relevant when Test Environment (COBOL tab) is set to z/OS.  However if you’ve set up Jazz with Micro Focus and an IDE (Visual Studio or Eclipse), you might still want to compile and test your programs with z/OS, perhaps first doing some testing with Test Environment = IDE and then some more testing with z/OS, so this section is not necessarily irrelevant to IDE users.

This section describes how to set up Jazz so that it will automatically upload the generated COBOL and JCL, run the jobs, and download the output.   We start by setting values in the z/OS tab.  We can edit our configuration at any time by clicking [Configure], and then the z/OS tab.

Set up: the z/OS tab

Here’s where you describe your z/OS set up.  So that Jazz can submit jobs for you: -

·         Enter your mainframe userid.  IBMUSER is my personal ID at my z/OS test facility: Change this!

·         Enter your mainframe password and repeat it. Passwords must be repeated exactly.  Even if your z/OS system doesn’t care, here the password and its copy are regarded as different if one uses a capital where the other does not.

NOTE 1.   These Mainframe Credentials are HELD ON YOUR LOCAL PC, they are NEVER transmitted back to Jazz Software or elsewhere outside your secure environment. 

NOTE 2.   Provided that port 21 is correctly set up (or whatever port you give in the Job Submission section) Jazz will detect that FTPS (File Transfer Protocol (Secure) is available and use this for all communication with the mainframe.

·         Edit the JOB Statement. This will become the //name JOB … statement at the start of your job. The default job statement is initially
      //@Jobname JOB  ,CLASS=A,MSGCLASS=H,NOTIFY=&SYSUID,COND=(8,LT)
Note that this has a job name of @Jobname: this is an example of a Jazz Symbolic Parameter, and will be replaced when the job is submitted. Read Jazz Symbolic Parameters if you want to understand more about these.

The JZL templates are written in the expectation that the condition code parameter, COND=(8,LT), is present, so if you edit the JOB statement then you should not remove it.

·         To the right of the pro-forma job statement is a list of options for the way in which your jobs will be named: -

·         @Userid + next suffix.  If I had given my userid in #1 above as “Robertb”, then jobs will be named “Robertb1”, “Robertb2”, to “Robertb0”, then “RobertbA” to “RobertbZ”, then restart at “Robertb1” again.

·         @Userid + [   ].   You can enter a character here: blank, 0 to 9, or A to Z.  All jobs will have the same name.

·         Program Name.  This is the name of the program (or CICS Map) that is being compiled.  For example, if you set this option and you’re compiling a program name “PFirst”, then the job will be called “PFirst”.

·         As written. If you choose this option you should also edit the pro-forma Job statement to replace @JobName with the name that you want to use. Every job you submit will have this name.

·         Set the values that you use as your default Project, Group, and Type in your mainframe ISPF sessions.

·         Give your ISPF and zOS library names according to your local standards, using @Parameters when relevant.  For example here the source library is defined as “@Project.@Group.SRCLIB” which becomes “IBMUSER.MANAJAZZ.SRCLIB”.

·         Give the IP address of your zOS system so that Jazz can use FTP to submit jobs. 123.123.123.123 is a dummy address, but without a real address that will recognize the IBM Userid and password Jazz can’t communication with your zOS system.  Ask your system programmer for the appropriate IP address and Port number for FTP access to your z/OS system. If this setup is incorrect or if the zOS FTP system is not available when you click [Submit] then Jazz will create JCL but will not submit it.

·         If you are developing web service programs, set the details in this section as described in the relevant users’ guide page.   You might prefer to come back to this after your initial Jazz setup

You won’t need to set the Web Services section of this tab yet.  Close the Configure form to return to the Jazz workbench:-

Processing

We’ve used [Check] to get Jazz to check our program for mistakes.  Now we’re ready to generate a COBOL program and compile it.  Right-click the [Process] button. The Process form appears: -

Uncheck “Show this form on left click” so that in the future we can simply click [Process] and have Jazz automatically create COBOL, JCL, submit the job, and then retrieve the output.  Of course it is often convenient to right-click, and then take the process step-by-step from [Check] to [Submit]

1.1.   Click [Generate] and Jazz will create a COBOL program, PFirst.CBL.  [Find COBOL] will change to [Review COBOL], and in “Restart from Step” JCL is checked: -

1.2.   Click [Review COBOL] to see the COBOL program that Jazz has generated for us.   If you do not have a COBOL compiler on your PC then it may not recognise files with a .CBL extension, in which case the Windows dialog will ask you to select a program for such files.  Select Notepad.

Test a COBOL Compile

With the correct IP address and Port to access your z/OS system, and your Userid and Password entered, you should now have done enough to compile (but not yet run) batch programs.  Try this out with program PFirst.  We can’t run it because file PFirstR doesn’t exist on the mainframe, but we should be able to submit and compile the program: -

1.      Open the Jazz Workbench with program PFirst, as above.

2.      Right-click [Process] to display the Process form

3.      Click [Compile]  This will

·         re-check the program,

·         generate COBOL,

·         create appropriate JCL,

  • submit the job,

and then

  • check for output. 

When the button [Job Results] turns green we can click this to see the output.  If everything is set up correctly we’ll see a job that has compiled and linked our COBOL program.  

This will have tested template JZCompilebatch.jzl.   Other templates haven’t been tested yet.  We might need to edit the JZL (Jazz-format JCL) templates.

Edit JZL Templates

When you click [Process] from the Jazz Workbench, or right-click [Process] and then click [Submit] button on the Process form, Jazz will create a job stream to compile [and run] your job.   It uses JZL templates to do this: these templates were installed when you clicked the [Initialize Project] button in Set Up, Step 1.  Configure Jazz above.   JZL templates have extension “.jzl”, they are normal z/OS JCL except that

1.      They may contain Jazz symbolic parameters, names like “@Jobname” that start with “@” and are known to Jazz.  They may also include normal z/OS symbolic parameters: these start with “&”. 

2.      They may be longer than the 72-character maximum length of standard z/OS JCL.  When Jazz converts them to JCL to create a job it will handle continuation characters and break the over-length line at an appropriate point.

Probably the templates won’t need much changing at this stage (you can always change them later), but in case you want to review them here is a list: -

Name

Function

JZAssembleMap.jzl

Compile (assemble) a BMS map.  This is automatically done from the Jazz screen editor when you click [Process]

JZCompilebatch.jzl

JCL for compiling and linking a batch program

JZCompilebatchSQL.jzl

JCL for compiling and linking a batch program that uses SQL (DB2, Oracle, etc).  See Note 1

JZCompileCICS.jzl

JZL for compiling and linking a CICS program

JZCompileCICSSQL.jzl

JZL for compiling and linking a CICS program that uses SQL (DB2, Oracle, etc).  See Note 1

JZGENER.jzl

An IEBGENER step.  Not used now

JZGO.jzl

JZL that is used for the GO step of a batch job (which is the only step if you submit a run-only job).  This includes a few standard DD statements: in addition extra DD statements will be generated from DEFINE statements that include a DSNAME option.  All these extra DD statements will have DSNAME options and DISP=SHR and so you will need to modify the JCL if your job is creating a new data set (requires DISP=(NEW,KEEP) and a SPACE parameter), or is updating it and requires DISP=OLD to give it exclusive access.

JZJobProc.jzl

A JCLLIB statement that is used with Web Service jobs

JZWSProv.jzl

Used for Web Service Provider programs

JZWSReq.jzl

Used for Web Service Requester programs

 

Note 1.  These SQL procedures have been included for our own (Jazz Software Ltd) own testing.  SQL features have been tested using a local copy of DB2 and Micro Focus Enterprise Developer with Visual Studio, to SQL has not been tested with a mainframe DB2 database yet.  These JZL procedures have not been proven correct and need to be checked: however like all JZL templates they will normally need local modification anyway.

Compile Support Subprograms

Download and compile JZxxxx routines that may be required by your program.  Click here (or the heading) for details.

Validate remaining templates

After the steps above have been completed then

1.                  Using a small mainframe sequential test file,

a.      Import its COBOL record layout into Jazz, and edit it to add missing information such as its DSNAME.

b.      Write a simple batch program to print a report from it.  This will test that the JZGO template is correct for you.

2.                  If you are going to be writing Classical CICS programs you should

a.      Examine the supplied 3270 screen template, TMPL01.  If you wish to have a template that reflects your local standards, you can either create a new one with a different name, or edit TMPL01. 

b.      Examine, and edit if necessary, the JZL templates JZAssembleMap for assembling screen maps, and JZCompileCICS for compiling CICS programs.

c.      Test these by creating a basic CICS program such as CICS2, at least to the stage of proving that the screen and program compile correctly.

d.      You may need help from your system programmer to ensure that your CICS test system is correctly set up.  CICS setup is not the responsibility of Jazz.

3.                  If you are going to be writing Web Service programs you should

a.      Examine, and edit if necessary, the JZL templates JZJobProc, JZWSProv, and JZWSReq.  

b.      Create a simple web service and test it, as described in the web pages JazzUGSOA1.htm and JazzUGSOA2_files .  

c.      You will need help from your system programmer to get your first web service program running. 

Set Up Jazz to work with Micro Focus and an IDE

See JazzUGMFStep1.htm

Appendices

General information.

Jazz Extensions

Various folders store Jazz Programs, Copy Books, Screens, JCL, and other types of objects. By giving the same folder name for Jazz Programs, Jazz Copy Code, etc you could use a single folder for all these different types as Jazz uses the filename extension to denote the type of object, and there may be many objects with the same basic name but with different extensions. This is different to the mainframe world where one PDS holds COBOL programs, another holds JCL, and so on.

Jazz currently recognizes the following extensions/object types: -

.CBL    COBOL program (generated by Jazz, or from an external source (e.g., downloaded from zOS when converting COBOL to Jazz))

.JCL    z/OS JCL.  May be produced as a result of [Submit] being clicked, and built from various .JZL templates.

.jzc       Jazz Copy Book.  One or more DEFINE statements, and/or COPY statements.   One of the DEFINE statements should have the same name as the copy book.

.jzd       Jazz Data Dictionary.  This extension is reserved for a future development, in which Jazz will record data usage across all the programs of a project.  It has XML format.

.jzl        Jazz-format JCL.  This is essentially standard z/OS JCL except that it may contain Jazz parameters, and JCL statements can be of any length.  Both JCL and COBOL statements may initially extend beyond column 72: this is sorted out when the JCL and COBOL is written out.

.jzm     CICS 3270-type screen map. Used to generate the physical map used in classical CICS screens.

.jzs       Jazz 3270-type screen. This contains both layout and data type rules, and is edited by the Jazz Screen Editor

.jzt        Jazz templates.  These are templates for various types of programs.  Note that the templates are very basic, mostly the form of the generated program is controlled by the logic in the Jazz Workbench.

.jzx       XML.

.jzw      Web service descriptions. XML documents describing the web services that Jazz has discovered. These are somewhat simplified compared to the original WSDL, containing only the information that Jazz needs.

.jzz       Jazz Program.  This code should start with PROGRAM xxx or SUBPROGRAM xxx, where ‘xxx’ is the name of the .jzz object.

.txt       Text.  Jazz uses this when downloading jobs.

.xls       Excel Spreadsheets

.xlsx     Excel Spreadsheets

Various Issues

Jazz has been built with the option “The application is available offline as well (launchable from Start menu)” and so it will install on your computer, although it is sandboxed by Microsoft’s ClickOnce technology, and so can’t access your Windows system except the folders that you define with your Jazz configuration. This will enable you to run it for a while without being connected to the JazzSoftware.co.nz web site, but it will check to see if an update is available when you start Jazz.  We have chosen this option so that you are not inconvenienced by breaks in service from the Internet or the Jazz web site.  However Help requires the web site to be available.  You will need to access the web site at least monthly.

Jazz can only access your mainframe in the same way as a COBOL application programmer using TSO: it has no special privileges or its own LPAR, and NOTHING is installed on the mainframe except for the minor subprograms described in Compile Support Subprograms.  Our expectation is that you configure z/OS access only to your test environment (batch and CICS), continuing to follow the same procedures for promoting developed programs from test to production as you do now, and using the same software tools as you would when you’re writing programs manually.

Jazz is at an early stage and we expect errors and missing features.  Let us know of any problems you find, and suggestions for improvement.

Trouble-Shooting Installation

Jazz is delivered as a Microsoft ClickOnce program: click the Run Jazz link and Jazz should start up and install itself on your computer.  If Jazz does not install cleanly from the web site www.jazzsoftware.co.nz, then the most likely cause is that you’re using a browser that does not have support for Microsoft ClickOnce programs.  To confirm this, try Run Jazz using Internet Explorer or Edge.

The simplest fix for this problem: install Jazz using a Microsoft browser (Internet Explorer or Edge).  You don’t have to make this your default browser if you prefer to keep using Chrome or another: from now on you’ll start Jazz by clicking the icon that you’ve put on your desktop or taskbar.

You can install with Firefox, Chrome, etc by installing an AddIn. Google xxxx ClickOnce (e.g. “Chrome ClickOnce”).

Various error symptoms when using Chrome

We have seen the following error symptoms when an attempt has been made to install Jazz from a page opened by Chrome without ClickOnce support.

For example, when an attempt was made to install Jazz using the standard Chrome browser you may just see some message about Javascript, but nothing actually happens.  Or Jazz may start and then display various messages, as below.  We’ll add to this list as we are notified of them

1.         There were various Javascript messages, but nothing else seemed to happen and Jazz doesn’t start.

2.         Jazz downloaded and displayed the configuration form, and everything appeared to work as normal until it reached the point where the Jazz Workbench should have been displayed.   At that point this message was displayed: -

This error is incorrect: the Jazz web site would have sent a license token, the problem is that the browser is not recognising it.   Clicking [OK] leads to: -

and [Continue] leads to further errors.

3.         An earlier version of Jazz reported the error as: -

On clicking [Details] you saw something like this: -

PLATFORM VERSION INFO

       Information about your Windows environment

 

SOURCES

       Deployment url                    : Where it was installed/Jazz.application

 

IDENTITIES

       Deployment Identity        : Jazz.application, Version=1.13.7.111, Culture=neutral, PublicKeyToken=4a9f8c94079d1f42, processorArchitecture=x86

 

APPLICATION SUMMARY

       * Installable application.

       * Trust url parameter is set.

ERROR SUMMARY

       Below is a summary of the errors, details of these errors are listed later in the log.

       * Activation of Where it was installed\Jazz.application resulted in exception. Following failure messages were detected:

              + Deployment and application do not have matching security zones.

More diagnostic information

Glossary 

.NET

Microsoft’s development framework – a series of support classes used by programs generated with Visual Studio.

BMS

Basic Mapping Support.  The technology (Assembler Macros) used to describe 3270-type screens, i.e. the “Green screens” of Classical CICS

CICS

Customer Information Control System.  IBM Operating System software to manage many simultaneous on-line users.

FTP

File Transfer Protocol.  The protocol used when one computer sends or receives files from another.

FTPS

File Transfer Protocol Secure.  A variation of FTP in which the transmitted data is encrypted, so that it cannot be interfered with by intermediate computers in the path from sending computer to receiving computer.  Jazz will automatically use FTPS if its “FTP Handshake” detects that the other end is configured for automatic FTPS.

HTML

Hypertext Markup Language.   Defines a syntax like <tag>text</tag> that allows you to specify markup, controlling the appearance of text.  For example <B>Word</B> specifies that Word should be displayed as Bold.

HTTP

HyperText Transfer Protocol.   The protocol used to transmit HTML, for example to send a web page for display.

IDE

Integrated Development Environment.   For example Visual Studio (Microsoft), Eclipse (Open Source)

JCL

Job Control Language.  A “Language” to control batch job streams, defining jobs, job steps, and files.

LAN

Local Area Network.   Computers (usually Laptops and PC’s) linked together in an office, typically with a shared server where common files can be saved.

LPAR

Logical PARtition.   A region of a shared z/OS mainframe, keeping the users, files, and other resources separate from other LPARs.

MF

Micro Focus

MFED

Micro Focus Enterprise Developer

TSO

Time Share Option.   A facility of z/OS used for program development and system management.

VS

Visual Studio

XML

eXtensible Markup Language.  Whereas basic HTML uses standard tags like <B> and <P> (paragraph), XML allows you to define your own tags, for example <AccountNbr>123456</AccountNbr>.   This allows messages to be transmitted with HTTP that can be understood by both receiving and sending programs sharing an XML schema

z/OS

Z-series Operating System.  The operating system for IBM Enterprise Computers (“Z-Series”)