[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job

106 views
Skip to first unread message

daniel.stratton@response-systems.com (JIRA)

unread,
May 19, 2019, 8:32:02 PM5/19/19
to jenkinsc...@googlegroups.com
Daniel Stratton created an issue
 
Jenkins / Bug JENKINS-57549
Jenkins job doesn't detect completion of mainframe job
Issue Type: Bug Bug
Assignee: Alexander Shcherbakov
Components: zos-connector-plugin
Created: 2019-05-20 00:31
Environment: Jenkins 2.164.3
Priority: Minor Minor
Reporter: Daniel Stratton

After upgrading to version 2.3.0, our existing Jenkins freestyle jobs are failing when submitting a job to the mainframe.

Rolling back to 2.2.0 and resubmitting results in a working environment again.

Failure logs look like:
07:38:22 FTP: connected to 172.29.122.117:21*07:38:23* Submitted job [JOB01556]07:38:33 ERROR: Job [JOB01556] cannot be found in JES*07:38:44* ERROR: Job [JOB01556] cannot be found in JES
...
10:04:07 ERROR: Job [JOB01556] cannot be found in JES
10:04:15 ERROR: Interrupted.
10:04:15 Job [JOB01556] processing failed. Reason: [WAIT_INTERRUPTED]
10:04:18 ERROR: z/OS job failed with CC WAIT_INTERRUPTED
Which is the point the jenkins job was killed.

Prior version looks like:
10:09:19 FTP: connected to 172.29.122.117:21*10:09:20* Submitted job [JOB01575]10:09:30 FTP: connected to 172.29.122.117:21*10:09:30* FTP: connected to 172.29.122.117:21*10:09:32* FTP: connected to 172.29.122.117:21*10:09:41* ERROR: Failed to log out from FTP server*10:09:41* FTP: connected to 172.29.122.117:21*10:09:42* Job [JOB01575] processing finished. Captured RC = [0000]
The job identified in 2.3.0 did get submitted, did run and did end with RC=0.

 

 

16.44.49 JOB01556 ---- SUNDAY, 19 MAY 2019 ---- 
16.44.49 JOB01556 IRR010I USERID JENKINS IS ASSIGNED TO THIS JOB. 
16.44.49 JOB01556 ICH70001I JENKINS LAST ACCESS AT 16:44:48 ON SUNDAY, MAY 19, 2019
16.44.49 JOB01556 $HASP373 GEN65CAS STARTED - INIT 1 - CLASS A - SYS S0W1
...
16.44.50 JOB01556 - -----TIMINGS (MINS.)------ -----PAGING COUNTS----
16.44.50 JOB01556 -STEPNAME PROCSTEP RC EXCP CONN TCB SRB CLOCK SERV WORKLOAD PAGE SWAP VIO SWAPS
16.44.50 JOB01556 -KEYS CAIRIM 00 302 113 .00 .00 .0 30 BATCH 0 0 0 0
16.44.50 JOB01556 -GEN65CAS ENDED. NAME- TOTAL TCB CPU TIME= .00 TOTAL ELAPSED TIME= .0 
16.44.50 JOB01556 $HASP395 GEN65CAS ENDED - RC=0000
------ JES2 JOB STATISTICS ------ 
 19 MAY 2019 JOB EXECUTION DATE 
 17 CARDS READ 
 208 SYSOUT PRINT RECORDS 
 0 SYSOUT PUNCH RECORDS 
 16 SYSOUT SPOOL KBYTES 
 0.00 MINUTES EXECUTION TIME

 

 
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

daniel.stratton@response-systems.com (JIRA)

unread,
May 19, 2019, 8:40:03 PM5/19/19
to jenkinsc...@googlegroups.com
Daniel Stratton updated an issue
Change By: Daniel Stratton
After upgrading to version 2.3.0, our existing Jenkins freestyle jobs are failing when submitting a job to the mainframe.

Rolling back to 2.2.0 and resubmitting results in a working environment again.

Failure logs look like:
* {noformat}
 07:38:22 * FTP: connected to 172.29.122.117:21 *
07:38:23 * Submitted job [JOB01556] *
07:38:33 * ERROR: Job [JOB01556] cannot be found in JES *
07:38:44 * ERROR: Job [JOB01556] cannot be found in JES

...
10:04:07 ERROR: Job [JOB01556] cannot be found in JES
10:04:15 ERROR: Interrupted.
10:04:15 Job [JOB01556] processing failed. Reason: [WAIT_INTERRUPTED]
10:04:18 ERROR: z/OS job failed with CC WAIT_INTERRUPTED {noformat}
Which is the point the jenkins job was killed.

Prior version looks like:
* {noformat}
 10:09:19 * FTP: connected to 172.29.122.117:21 *
10:09:20 * Submitted job [JOB01575] *
10:09:30 * FTP: connected to 172.29.122.117:21 *
10:09:30 * FTP: connected to 172.29.122.117:21 *
10:09:32 * FTP: connected to 172.29.122.117:21 *
10:09:41 * ERROR: Failed to log out from FTP server *
10:09:41 * FTP: connected to 172.29.122.117:21 *
10:09:42 * Job [JOB01575] processing finished. Captured RC = [0000] {noformat}
The job identified in 2.3.0 did get submitted, did run and did end with RC=0.

 

 
 {code:java}

16.44.49 JOB01556 ---- SUNDAY, 19 MAY 2019 ----
16.44.49 JOB01556 IRR010I USERID JENKINS IS ASSIGNED TO THIS JOB.
16.44.49 JOB01556 ICH70001I JENKINS LAST ACCESS AT 16:44:48 ON SUNDAY, MAY 19, 2019
16.44.49 JOB01556 $HASP373 GEN65CAS STARTED - INIT 1 - CLASS A - SYS S0W1
...
16.44.50 JOB01556 - -----TIMINGS (MINS.)------ -----PAGING COUNTS----
16.44.50 JOB01556 -STEPNAME PROCSTEP RC EXCP CONN TCB SRB CLOCK SERV WORKLOAD PAGE SWAP VIO SWAPS
16.44.50 JOB01556 -KEYS CAIRIM 00 302 113 .00 .00 .0 30 BATCH 0 0 0 0
16.44.50 JOB01556 -GEN65CAS ENDED. NAME- TOTAL TCB CPU TIME= .00 TOTAL ELAPSED TIME= .0
16.44.50 JOB01556 $HASP395 GEN65CAS ENDED - RC=0000
------ JES2 JOB STATISTICS ------
19 MAY 2019 JOB EXECUTION DATE
17 CARDS READ
208 SYSOUT PRINT RECORDS
0 SYSOUT PUNCH RECORDS
16 SYSOUT SPOOL KBYTES
0.00 MINUTES EXECUTION TIME
{code}
 

 

candiduslynx@gmail.com (JIRA)

unread,
May 19, 2019, 10:38:02 PM5/19/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov started work on Bug JENKINS-57549
 
Change By: Alexander Shcherbakov
Status: Open In Progress

candiduslynx@gmail.com (JIRA)

unread,
May 19, 2019, 10:39:02 PM5/19/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov commented on Bug JENKINS-57549
 
Re: Jenkins job doesn't detect completion of mainframe job

Looks like regression from 2.3.0 changes.

Tell me please, what JESINTERFACELEVEL is set on mainframe and in the Jenkins build step config?

 

candiduslynx@gmail.com (JIRA)

unread,
May 19, 2019, 10:46:02 PM5/19/19
to jenkinsc...@googlegroups.com
Looks like regression from 2.3.0 changes.

Tell me please, what JESINTERFACELEVEL is set on mainframe and in the Jenkins build step config?
Also, kindly log onto mainframe via FTP manually and perform the following command sequence (post the log back, please, as attachhment):

1. {{quote site   filetype=jes jesjobname=* jesstatus=ALL jesentrylimit=1024}}

2. {{NLST}}

3. {{LIST}}

Also try without jesentrylimit, see if it will give you any differences.

daniel.stratton@response-systems.com (JIRA)

unread,
May 19, 2019, 11:09:01 PM5/19/19
to jenkinsc...@googlegroups.com

I believe I'm JESINTERFACELEVEL 2, and the job has the checkbox cleared.

I'm not sure the best way to getting what you want - how would I issue NLST and LIST?  I'm used to the DOS command prompt which accepts the quote site command.  Is that just issuing DIR and LS?

I'll reach out to a colleague for the details on our connection, as the password used by Jenkins is not globally visible and I don't know it off hand.

I'll try to respond within 8 hours if I can.

daniel.stratton@response-systems.com (JIRA)

unread,
May 20, 2019, 6:23:02 AM5/20/19
to jenkinsc...@googlegroups.com
Daniel Stratton updated an issue
Change By: Daniel Stratton
Attachment: listing.nolimit.txt
Attachment: listing.txt

daniel.stratton@response-systems.com (JIRA)

unread,
May 20, 2019, 6:28:02 AM5/20/19
to jenkinsc...@googlegroups.com
 
Re: Jenkins job doesn't detect completion of mainframe job

The listings look the same to me, beyond obvious differences in timings/timestamps.  And the list doesn't look super long (certainly not 1024).  Even if I put JESOWNER=* in there I only get to 450 or so entries.

Happy to provide anything else you need, thanks.

candiduslynx@gmail.com (JIRA)

unread,
May 20, 2019, 12:50:02 PM5/20/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov updated an issue
 
Change By: Alexander Shcherbakov
Attachment: zos-connector.hpi

candiduslynx@gmail.com (JIRA)

unread,
May 20, 2019, 12:51:04 PM5/20/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov commented on Bug JENKINS-57549
 
Re: Jenkins job doesn't detect completion of mainframe job

I've just uploaded debug version: the issue is somewhat strange and maybe related to relogon logic differing from 2.2.0.

The code is in separate branch at GitHub as well.

daniel.stratton@response-systems.com (JIRA)

unread,
May 20, 2019, 7:52:01 PM5/20/19
to jenkinsc...@googlegroups.com
Daniel Stratton updated an issue
 
Change By: Daniel Stratton
Attachment: debugLog.20190521.0946.txt
Attachment: ftpLog.20190521.0946.txt

daniel.stratton@response-systems.com (JIRA)

unread,
May 20, 2019, 7:54:01 PM5/20/19
to jenkinsc...@googlegroups.com
Daniel Stratton commented on Bug JENKINS-57549
 
Re: Jenkins job doesn't detect completion of mainframe job

Appreciate the quick turnaround. 

I've attached the Console Output for the job, and an FTP query to prove the job is completed.  I was forced to cancel it as it just sat and spun in the same loop.

candiduslynx@gmail.com (JIRA)

unread,
May 21, 2019, 1:32:02 AM5/21/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov updated an issue
 
Change By: Alexander Shcherbakov
Attachment: zos-connector.hpi

candiduslynx@gmail.com (JIRA)

unread,
May 21, 2019, 1:32:02 AM5/21/19
to jenkinsc...@googlegroups.com

candiduslynx@gmail.com (JIRA)

unread,
May 21, 2019, 1:33:02 AM5/21/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov commented on Bug JENKINS-57549
 
Re: Jenkins job doesn't detect completion of mainframe job

OK, I decided to give more thought to the relogon logic - seems to be the reason.

For now - new dbg version + old SITE command. Kindly retest.

daniel.stratton@response-systems.com (JIRA)

unread,
May 21, 2019, 1:55:03 AM5/21/19
to jenkinsc...@googlegroups.com
Daniel Stratton updated an issue
 
Change By: Daniel Stratton
Attachment: jobConfig.png
Attachment: debugLog.20190521.1551.txt

daniel.stratton@response-systems.com (JIRA)

unread,
May 21, 2019, 1:57:02 AM5/21/19
to jenkinsc...@googlegroups.com
Daniel Stratton commented on Bug JENKINS-57549
 
Re: Jenkins job doesn't detect completion of mainframe job

New debug log, and a screenshot of the configuration of the job.  Strange how it's complaining about a filter change, given manual FTP commands are showing it works.

 

candiduslynx@gmail.com (JIRA)

unread,
May 21, 2019, 2:08:03 AM5/21/19
to jenkinsc...@googlegroups.com

Kindly check the RACF settings mentioned in this article:

https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.halu001/intfjessecchange.htm

It is also really strange, given the fact that 'listing' logs suggest the JENKINS user is authorized.

If you check that the issue is visible with debugging version and then downgrade to 2.2.0, is the issue gone?

The config of the job not changing between these 2 submissions?

candiduslynx@gmail.com (JIRA)

unread,
May 21, 2019, 2:16:02 AM5/21/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov updated an issue
 
Change By: Alexander Shcherbakov
Attachment: zos-connector.hpi

candiduslynx@gmail.com (JIRA)

unread,
May 21, 2019, 2:18:02 AM5/21/19
to jenkinsc...@googlegroups.com

daniel.stratton@response-systems.com (JIRA)

unread,
May 21, 2019, 2:22:03 AM5/21/19
to jenkinsc...@googlegroups.com
Daniel Stratton commented on Bug JENKINS-57549
 
Re: Jenkins job doesn't detect completion of mainframe job

I'm escalating this up internally my side - RACF isn't something I have access to, nor knowledge of.

But I just used "Manage Plugins" to rollback to 2.2.0, restarted Jenkins, hit the Build now button, and it successfully ran.

No change to job configuration.  We have Job History plugin installed, and the last change on that was in March when we migrated from 1.2.6.1 to to 2.2.0 and moved our JCL into source control.

candiduslynx@gmail.com (JIRA)

unread,
May 21, 2019, 2:23:01 AM5/21/19
to jenkinsc...@googlegroups.com

Also, I've uploaded new version with slightly changed connect logic, maybe this can also help.

Kindly test with it.

candiduslynx@gmail.com (JIRA)

unread,
May 21, 2019, 2:32:02 AM5/21/19
to jenkinsc...@googlegroups.com

And the version with old logic for relogon (logout, reconnect, logon vs reconnect + rein). - Kindly test this one, too.

candiduslynx@gmail.com (JIRA)

unread,
May 21, 2019, 2:32:02 AM5/21/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov updated an issue
Change By: Alexander Shcherbakov
Attachment: zos-connector-logout-instead-rein.hpi

daniel.stratton@response-systems.com (JIRA)

unread,
May 21, 2019, 8:03:02 AM5/21/19
to jenkinsc...@googlegroups.com
Daniel Stratton updated an issue
Change By: Daniel Stratton
Attachment: debugLog.20190521.2047.txt
Attachment: debugLog.20190521.2012.txt

daniel.stratton@response-systems.com (JIRA)

unread,
May 21, 2019, 8:03:02 AM5/21/19
to jenkinsc...@googlegroups.com
Daniel Stratton commented on Bug JENKINS-57549
 
Re: Jenkins job doesn't detect completion of mainframe job

Sorry mate, but they're both failing in the same way for me.  It connects, but doesn't sub, and 5 minutes later it times out and fails the job.

candiduslynx@gmail.com (JIRA)

unread,
May 21, 2019, 10:56:02 AM5/21/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov updated an issue
 
Change By: Alexander Shcherbakov
Attachment: zos-connector-explicit-logs.hpi

candiduslynx@gmail.com (JIRA)

unread,
May 21, 2019, 10:56:02 AM5/21/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov commented on Bug JENKINS-57549
 
Re: Jenkins job doesn't detect completion of mainframe job

OK, need to dig more logs - made just explicit logs on reconnect and relogon (new .hpi).

Waiting for new logs.

daniel.stratton@response-systems.com (JIRA)

unread,
May 21, 2019, 7:25:02 PM5/21/19
to jenkinsc...@googlegroups.com
Daniel Stratton updated an issue
 
Change By: Daniel Stratton
Attachment: debugLog.20190522.0921.txt

candiduslynx@gmail.com (JIRA)

unread,
May 22, 2019, 5:50:03 AM5/22/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov updated an issue
Change By: Alexander Shcherbakov
Attachment: zos-connector.hpi

candiduslynx@gmail.com (JIRA)

unread,
May 22, 2019, 5:50:04 AM5/22/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov updated an issue
Change By: Alexander Shcherbakov
Attachment: zos-connector-relogon-debug-1.hpi

candiduslynx@gmail.com (JIRA)

unread,
May 22, 2019, 5:51:03 AM5/22/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov updated an issue
Change By: Alexander Shcherbakov
Attachment: zos-connector-logout-instead-rein.hpi

candiduslynx@gmail.com (JIRA)

unread,
May 22, 2019, 5:51:03 AM5/22/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov updated an issue
Change By: Alexander Shcherbakov
Attachment: zos-connector-explicit-logs.hpi

candiduslynx@gmail.com (JIRA)

unread,
May 22, 2019, 5:52:01 AM5/22/19
to jenkinsc...@googlegroups.com
 
Re: Jenkins job doesn't detect completion of mainframe job

updated with logs for logon err: need to see what happens there (as connections seems to be fine).

Suppose the rein works strangely with IBM FTP implementation, so I'd need to use logout/logon logic now.

daniel.stratton@response-systems.com (JIRA)

unread,
May 22, 2019, 6:43:02 AM5/22/19
to jenkinsc...@googlegroups.com
Daniel Stratton updated an issue
 
Change By: Daniel Stratton
Attachment: debugLog.20190522.2041.txt

daniel.stratton@response-systems.com (JIRA)

unread,
May 22, 2019, 6:43:02 AM5/22/19
to jenkinsc...@googlegroups.com
Daniel Stratton commented on Bug JENKINS-57549
 
Re: Jenkins job doesn't detect completion of mainframe job

Installed and ran it, then downgraded, installed and ran it again to confirm the results.  Seems much the same as your last one but for an exception missing.

candiduslynx@gmail.com (JIRA)

unread,
May 22, 2019, 7:24:05 AM5/22/19
to jenkinsc...@googlegroups.com

It differs a bit - now I know that there was IOException. Posting version that will print stacktrace for this.

candiduslynx@gmail.com (JIRA)

unread,
May 22, 2019, 7:24:08 AM5/22/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov updated an issue
 
Change By: Alexander Shcherbakov
Attachment: zos-connector-stacktrace.hpi

candiduslynx@gmail.com (JIRA)

unread,
May 22, 2019, 7:24:08 AM5/22/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov updated an issue
Change By: Alexander Shcherbakov
Attachment: zos-connector-relogon-debug-1.hpi

daniel.stratton@response-systems.com (JIRA)

unread,
May 22, 2019, 8:14:02 AM5/22/19
to jenkinsc...@googlegroups.com
Daniel Stratton commented on Bug JENKINS-57549
 
Re: Jenkins job doesn't detect completion of mainframe job

Log attached, looks like it's being closed server side because it idled out.

It's late here so I'll look for anything more you need from me tomorrow.

daniel.stratton@response-systems.com (JIRA)

unread,
May 22, 2019, 8:14:02 AM5/22/19
to jenkinsc...@googlegroups.com
Daniel Stratton updated an issue
 
Change By: Daniel Stratton
Attachment: debugLog.20190522.2212.txt

candiduslynx@gmail.com (JIRA)

unread,
May 22, 2019, 11:27:03 AM5/22/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov updated an issue
Change By: Alexander Shcherbakov
Attachment: zos-connector-local-passive-before-logon.hpi

candiduslynx@gmail.com (JIRA)

unread,
May 22, 2019, 11:30:02 AM5/22/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov commented on Bug JENKINS-57549
 
Re: Jenkins job doesn't detect completion of mainframe job

Found some thread about using local passive before logon. Try this ver, please.

candiduslynx@gmail.com (JIRA)

unread,
May 22, 2019, 11:30:02 AM5/22/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov updated an issue
Change By: Alexander Shcherbakov
Attachment: zos-connector-local-passive-after-conn.hpi

candiduslynx@gmail.com (JIRA)

unread,
May 22, 2019, 11:30:02 AM5/22/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov updated an issue
Change By: Alexander Shcherbakov
Attachment: zos-connector-local-passive-before-logon.hpi

candiduslynx@gmail.com (JIRA)

unread,
May 22, 2019, 11:30:02 AM5/22/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov updated an issue
Change By: Alexander Shcherbakov
Attachment: zos-connector-stacktrace.hpi

daniel.stratton@response-systems.com (JIRA)

unread,
May 22, 2019, 5:38:02 PM5/22/19
to jenkinsc...@googlegroups.com
Daniel Stratton updated an issue
Change By: Daniel Stratton
Attachment: debugLog.20190523.0736.txt

daniel.stratton@response-systems.com (JIRA)

unread,
May 22, 2019, 5:39:01 PM5/22/19
to jenkinsc...@googlegroups.com
Daniel Stratton commented on Bug JENKINS-57549
 
Re: Jenkins job doesn't detect completion of mainframe job

Looks fundamentally the same.  Whatever you used to do in 2.2.0 worked a treat on our side, albeit with some strange warnings.

candiduslynx@gmail.com (JIRA)

unread,
May 23, 2019, 4:25:01 AM5/23/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov updated an issue
 
Change By: Alexander Shcherbakov
Attachment: zos-connector-update-libs.hpi

candiduslynx@gmail.com (JIRA)

unread,
May 23, 2019, 4:26:03 AM5/23/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov commented on Bug JENKINS-57549
 
Re: Jenkins job doesn't detect completion of mainframe job

updated libs, issue disconnect always as in 2.2

candiduslynx@gmail.com (JIRA)

unread,
May 23, 2019, 4:26:04 AM5/23/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov updated an issue
Change By: Alexander Shcherbakov
Attachment: zos-connector-local-passive-after-conn.hpi

daniel.stratton@response-systems.com (JIRA)

unread,
May 23, 2019, 6:58:02 AM5/23/19
to jenkinsc...@googlegroups.com
Daniel Stratton updated an issue
Change By: Daniel Stratton
Attachment: debugLog.20190523.2055.txt

candiduslynx@gmail.com (JIRA)

unread,
May 23, 2019, 10:13:03 AM5/23/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov updated an issue
Change By: Alexander Shcherbakov
Attachment: zos-connector-restructure-relogon.hpi

candiduslynx@gmail.com (JIRA)

unread,
May 23, 2019, 10:13:03 AM5/23/19
to jenkinsc...@googlegroups.com
 
Re: Jenkins job doesn't detect completion of mainframe job

restructure relogon. Really strange place.

candiduslynx@gmail.com (JIRA)

unread,
May 23, 2019, 10:13:03 AM5/23/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov updated an issue
Change By: Alexander Shcherbakov
Attachment: zos-connector-update-libs.hpi

daniel.stratton@response-systems.com (JIRA)

unread,
May 23, 2019, 6:17:02 PM5/23/19
to jenkinsc...@googlegroups.com
Daniel Stratton updated an issue
Change By: Daniel Stratton
Attachment: debugLog.20190524.0815.txt

candiduslynx@gmail.com (JIRA)

unread,
May 24, 2019, 6:11:02 AM5/24/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov updated an issue
Change By: Alexander Shcherbakov
Attachment: zos-connector-restructure-relogon.hpi

candiduslynx@gmail.com (JIRA)

unread,
May 24, 2019, 6:11:03 AM5/24/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov updated an issue
Change By: Alexander Shcherbakov
Attachment: zos-connector-old-logon-connect.hpi

candiduslynx@gmail.com (JIRA)

unread,
May 24, 2019, 6:12:02 AM5/24/19
to jenkinsc...@googlegroups.com
 
Re: Jenkins job doesn't detect completion of mainframe job

copy-pasted old (2.2) logon and connect routines. Kindly retest with them.

This looks more and more strange: can it be somehow related to FTP server state?

daniel.stratton@response-systems.com (JIRA)

unread,
May 26, 2019, 6:02:02 PM5/26/19
to jenkinsc...@googlegroups.com
Daniel Stratton updated an issue
 
Change By: Daniel Stratton
Attachment: debugLog.20190527.0800.txt

daniel.stratton@response-systems.com (JIRA)

unread,
May 26, 2019, 6:04:02 PM5/26/19
to jenkinsc...@googlegroups.com
Daniel Stratton commented on Bug JENKINS-57549
 
Re: Jenkins job doesn't detect completion of mainframe job

Forward progress, but it's still stuck in a loop.  It can find the job, but for some reason seems unable to determine it has finished (and it most definitely has).

But now it's submitting and listing.

Can't offer you much insight from my side - for me, I can always just roll back to 2.2.0 and it works, albeit with extra messages.  Wish I knew more to offer insight.

This is a low volume usage mainframe (only a handful of developer users), so there won't be much churn on state

candiduslynx@gmail.com (JIRA)

unread,
May 27, 2019, 12:29:01 AM5/27/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov updated an issue
 
Change By: Alexander Shcherbakov
Attachment: zos-connector-old-logon-connect.hpi

candiduslynx@gmail.com (JIRA)

unread,
May 27, 2019, 12:31:01 AM5/27/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov commented on Bug JENKINS-57549
 
Re: Jenkins job doesn't detect completion of mainframe job

OK, I found the issue now. It seems that during restructuring changes for 2.3.0 I accidentally broke JESINTERFACELEVEL=2 check (it doesn't try to extract RC at all) by misplacing single '}'.

I decided to leave logon as in 2.2.0 (more stable) + fixed the rc check. Kindly retest.

candiduslynx@gmail.com (JIRA)

unread,
May 27, 2019, 12:31:02 AM5/27/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov updated an issue
Change By: Alexander Shcherbakov
Attachment: zos-connector.hpi

daniel.stratton@response-systems.com (JIRA)

unread,
May 27, 2019, 1:00:03 AM5/27/19
to jenkinsc...@googlegroups.com
Daniel Stratton updated an issue
Change By: Daniel Stratton
Attachment: debugLog.20190527.1456.txt

daniel.stratton@response-systems.com (JIRA)

unread,
May 27, 2019, 1:01:03 AM5/27/19
to jenkinsc...@googlegroups.com
Daniel Stratton commented on Bug JENKINS-57549
 
Re: Jenkins job doesn't detect completion of mainframe job

I've run 3 successful jobs back to back with no obvious signs of problems, so it looks to be good from my side.

candiduslynx@gmail.com (JIRA)

unread,
May 27, 2019, 1:22:01 AM5/27/19
to jenkinsc...@googlegroups.com
Alexander Shcherbakov resolved as Fixed
 

You can either wait for the plugin to be listed via Jenkins (or force yor server to list manually) or dl from here: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/zos-connector/2.3.1

Kindly test and close the issue as appropriate.
Change By: Alexander Shcherbakov
Status: In Progress Resolved
Resolution: Fixed
Released As: zos-connector-2.3.1

daniel.stratton@response-systems.com (JIRA)

unread,
May 27, 2019, 8:15:02 PM5/27/19
to jenkinsc...@googlegroups.com
 
Re: Jenkins job doesn't detect completion of mainframe job

Refreshed the plugin list from Jenkins, grabbed the last and ran a couple of jobs happily.

Thanks for getting this sorted.

daniel.stratton@response-systems.com (JIRA)

unread,
May 27, 2019, 8:16:02 PM5/27/19
to jenkinsc...@googlegroups.com
Daniel Stratton closed an issue as Fixed
 

Existing jobs are now working again quite happily.
Change By: Daniel Stratton
Status: Resolved Closed
Reply all
Reply to author
Forward
0 new messages