Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Excerpt

IBM z/OS Connector is a plugin which lets you connect your Jenkins to z/OS.

Table of Contents
Wiki Markup
{jenkins-plugin-info:pluginId=zos-connector}

What's new?

  • 1.2.0 – add JobName to output log file name. Change log file naming convention.
  • 1.1.1 – add environment variables expansion for "Submit z/OS job" build step. Add loggers.
  • 1.1.0 – add MaxCC papameter to 'Submit z/OS job' build step (see JENKINS-29214)
  • 1.0.4 – add support for 'RC unknown'
  • 1.0.3 – fix for JENKINS-29173


Build StatusImage Added

About

This plugin provides its functions via FTP connection to IBM z/OS LPAR. You can configure your SCLM project on z/OS and then check for the changes via Jenkins.

...

  • Introduction of SCLM as SCM for your projects allowing to ceckout checkout SCLM changes
    • The ability to build SCLM projects currently can be performed only via 'Submit zOS Job' build action
Note
titleVersion differences

Kindly back up your JCL texts before upgrading to version 2.0.0.
The 2.0 release uses text files instead of plaintext input, so old jobs will become obsolete.

Configuration

Note
titleJESINTERFACELEVEL differences

Job Name _must_ be configured accordingly to your FTP server configuration:

  • If JESINTERFACELEVEL=1 is configured, _only_ a job named USERIDx (USERID - your z/OS user ID, x - strictly 1 character) can be processed correctly (when you are waiting for the job to end).
  • If JESINTERFACELEVEL=2 is configiredconfigured, no additional considerations are required.

After you've installed IBM zOS Connector into your jenkins CI you will need to  do the following steps in order to enable its functionality.

SCLM integration

Image Removed

In the Jenkins CI project select 'SCLM' as SCM.

In the menu you have to configure the following parameters:

Parameter name

Description

Server

IBM z/OS LPAR name or IP address

Port

LPAR FTP port availible for communication

Username

z/OS User ID

Password

z/OS user password

Project

SCLM Project Name

Alternate

SCLM Project Alternate Definition

Group

SCLM Group to watch

Types

Comma-separated SCLM types you want to watch for changes (for example, HLASM, MACRO, JAVA, C, ...)

Additionally, you can specify custom job header and step for SCLM communication. 'Custom job step' means only the libraries needed for ISPF connection. Basically, if you have the standart z/OS installation you'll never need this. However, if the libraries you can see there are named differently or you want to use different version of them, please, define all the DDNames mentioned in the dropping text.

Code Block

//SCLMEX   EXEC PGM=IKJEFT01,REGION=4096K,TIME=1439,DYNAMNBR=200
//STEPLIB  DD DSN=ISP.SISPLPA,DISP=SHR
//         DD DSN=ISP.SISPLOAD,DISP=SHR
//ISPMLIB  DD DSN=ISP.SISPMENU,DISP=SHR
//ISPSLIB  DD DSN=ISP.SISPSENU,DISP=SHR
//         DD DSN=ISP.SISPSLIB,DISP=SHR
//ISPPLIB  DD DSN=ISP.SISPPENU,DISP=SHR
//ISPTLIB  DD UNIT=@TEMP0,DISP=(NEW,PASS),SPACE=(CYL,(1,1,5)),
//            DCB=(LRECL=80,BLKSIZE=19040,DSORG=PO,RECFM=FB),
//            DSN=
//         DD DSN=ISP.SISPTENU,DISP=SHR
//ISPTABL  DD UNIT=@TEMP0,DISP=(NEW,PASS),SPACE=(CYL,(1,1,5)),
//            DCB=(LRECL=80,BLKSIZE=19040,DSORG=PO,RECFM=FB),
//            DSN=
//ISPPROF  DD UNIT=@TEMP0,DISP=(NEW,PASS),SPACE=(CYL,(1,1,5)),
//            DCB=(LRECL=80,BLKSIZE=19040,DSORG=PO,RECFM=FB),
//            DSN=
//ISPLOG   DD SYSOUT=*,
//            DCB=(LRECL=120,BLKSIZE=2400,DSORG=PS,RECFM=FB)
//ISPCTL1  DD DISP=NEW,UNIT=@TEMP0,SPACE=(CYL,(1,1)),
//            DCB=(LRECL=80,BLKSIZE=800,RECFM=FB)
//SYSTERM  DD SYSOUT=*
//SYSPROC  DD DSN=ISP.SISPCLIB,DISP=SHR
//FLMMSGS  DD SYSOUT=(*)
//PASCERR  DD SYSOUT=(*)
//ZFLMDD   DD  *
   ZFLMNLST=FLMNLENU    ZFLMTRMT=ISR3278    ZDATEF=YY/MM/DD
/*
//SYSPRINT DD SYSOUT=(*)
//SYSTSPRT DD SYSOUT=(*)
Submitting JCL job

Image Removed

Firstly, select 'Submit z/OS job' in the Build Actions.

After that, fill in the following parameters (note that some of the parameters can be specified by system variables):

Parameter name

Description

Server

IBM z/OS LPAR name or IP address

Port

LPAR FTP port availible for communication

Username

z/OS User ID

Password

z/OS user password

Job

JCL of the job you want to be submitted

Additionally, you can make Jenkins CI wait for the job's completion. It will make Jankins CI save the joblog named

Code Block

Job_Name - [CC] (LPAR - JES_Job_ID) Jenkins_Project_name - Build_ID.log

If you want, you also may limit the time Jenkins waits for the job completion and add MaxCC (so that job which finished with CC=4 will be considered to be OK).
'Delete job log from Spool' allows Jenkins to delete the held job output upon job completion.

Environment variables

Currently IBM zOS Connector supports the following parameters of "Submit z/OS Job" build step to have any environment variables:

Parameter name

Description

Server

IBM z/OS LPAR name or IP address

Username

z/OS User ID

Password

z/OS user password

Job

JCL of the job you want to be submitted

MaxCC

The highest Condition Code job can have to be considered OK

Issue History

Jira Issues
renderModedynamic
width850px
anonymoustrue
urlhttp://issues.jenkins-ci.org/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=project+%3D+JENKINS+AND+component+%3D+zos-connector-plugin
height300px

Change log

Version 2.3.0
  • (error) Fix JESINTERFACELEVEL=1 inconsistencies (JENKINS-56976)
  • (warning) Don't do too many reconnects (regression from 2.2.0)
  • (lightbulb) Plugin can now handle RC in JESINTERFACELEVEL=1 (but you need to check that correct level is used in Jenkins job config)
Version 2.2.0
  • (warning) Logout of the FTP server as soon as single request is performed.
    This will result in increased number of connect → login → logout → disconnect sequences, but should also make plugin more stable.
Version 2.1.0
  • (warning) Environment variables are once again expanded before job submission (JENKINS-55609)
Version 2.0.1
  • (error) Fix false positive error message if not waiting on job completion (JENKINS-54574)
Version 2.0.0
  • (lightbulb) Use credentials instead of username-password pair
  • (lightbulb) Use text file with JCL code instead of plaintext field (if you need to track SCLM in the same job - consider using Multiple SCMs plugin)
Version 1.2.6.1
  • (lightbulb) Option to print JES job log
Version 1.2.6
  • (lightbulb) Update failure logic for slow JES initiators
Version 1.2.5
  • (warning) Use Jenkins 2+
Version 1.2.4.1
  • (warning) Add notification about incompatibility since 1.2.4.
Version 1.2.4
  • (lightbulb) Provide different messages into the build log based on the job completion code (JENKINS-31837)
Version 1.2.3
  • (error)   JESINTERFACELEVEL=1 output changes and configuration corrections.
Version 1.2.2
  • (plus)   JESINTERFACELEVEL=1 support.
Version 1.2.1
  • Dummy release
Version 1.2.0.2
Version 1.2.0.1
  • (error)   Add error message if job is not listed while waiting for its execution to end (possible problem with JESINTERFACELEVEL=1).
Version 1.2.0
  • (plus)   Add JobName to output log file name. Change log file naming convention.
Version 1.1.1
  • (plus)   Add environment variables expansion for "Submit z/OS job" build step. Add loggers.
Version 1.1.0
  • (plus)   Add MaxCC papameter to 'Submit z/OS job' build step (JENKINS-29214)
Version 1.0.4
  • (plus)   Add support for 'RC unknown'.
Version 1.0.3