You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2016/01/21 14:21:39 UTC
[jira] [Comment Edited] (NET-587) MVSTPEntryParser extension for
JES2 listing other than output
[ https://issues.apache.org/jira/browse/NET-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110547#comment-15110547 ]
Sebb edited comment on NET-587 at 1/21/16 1:20 PM:
---------------------------------------------------
Hi
Below is sample output from FTP after switching to JES (site filetype=Jes).
JOBNAME JOBID OWNER STATUS CLASS
VCTPKO TSU01333 VCTPKO OUTPUT TSU ABEND=522 3 spool files
VCTPKO TSU01306 VCTPKO OUTPUT TSU ABEND=622 3 spool files
VCTPKO TSU01290 VCTPKO OUTPUT TSU ABEND=522 3 spool files
GENDBP2 JOB01267 VCTPKO OUTPUT S RC=0000 5 spool files
GENDBP2 JOB01266 VCTPKO OUTPUT S RC=0000 5 spool files
GENDBP2 JOB01264 VCTPKO OUTPUT S RC=0000 6 spool files
GENDBP2 JOB01263 VCTPKO OUTPUT S RC=0012 4 spool files
GENDBP2 JOB01262 VCTPKO OUTPUT S RC=0012 4 spool files
GENDBP2 JOB01261 VCTPKO OUTPUT A (JCL error) 3 spool files
IEFBR14 JOB01417 VCTPKO INPUT U
ENQDEQMN JOB00759 VCTPKO ACTIVE S
If you try to get output from the same server using FtpClient, you will see only entries with OUTPUT status.
FTP interface to JES is very popular way to to check the status of jobs (tasks executing in system).
In example above there are 3 different cases:
INPUT - the job was started but wait for execution because job initiator for class U is unavailable.
ACTIVE - the job is running and genereate results to SPOOL (some specific JES filesystem)
OUTPUT - the job was finished and files in SPOOL are ready to get
Regards
Piotr
was (Author: nutilius):
Hi
Below is sample output from FTP after sitching to JES (site filetype=Jes).
JOBNAME JOBID OWNER STATUS CLASS
VCTPKO TSU01333 VCTPKO OUTPUT TSU ABEND=522 3 spool files
VCTPKO TSU01306 VCTPKO OUTPUT TSU ABEND=622 3 spool files
VCTPKO TSU01290 VCTPKO OUTPUT TSU ABEND=522 3 spool files
GENDBP2 JOB01267 VCTPKO OUTPUT S RC=0000 5 spool files
GENDBP2 JOB01266 VCTPKO OUTPUT S RC=0000 5 spool files
GENDBP2 JOB01264 VCTPKO OUTPUT S RC=0000 6 spool files
GENDBP2 JOB01263 VCTPKO OUTPUT S RC=0012 4 spool files
GENDBP2 JOB01262 VCTPKO OUTPUT S RC=0012 4 spool files
GENDBP2 JOB01261 VCTPKO OUTPUT A (JCL error) 3 spool files
IEFBR14 JOB01417 VCTPKO INPUT U
ENQDEQMN JOB00759 VCTPKO ACTIVE S
If you try to get output from the same server using FtpClient, you will see only entries with OUTPUT status.
FTP interface to JES is very popular way to to check the status of jobs (tasks executing in system).
In example above there are 3 different cases:
INPUT - the job was started but wait for execution because job initiator for class U is unavailable.
ACTIVE - the job is running and genereate results to SPOOL (some specific JES filesystem)
OUTPUT - the job was finished and files in SPOOL are ready to get
Regards
Piotr
> MVSTPEntryParser extension for JES2 listing other than output
> -------------------------------------------------------------
>
> Key: NET-587
> URL: https://issues.apache.org/jira/browse/NET-587
> Project: Commons Net
> Issue Type: Improvement
> Components: FTP
> Affects Versions: 3.4
> Reporter: Piotr Kolasiński
> Priority: Minor
> Labels: features
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> In MVSFTPEntryParser only entries with OUTPUT status are inclis not usable in uded into listFiles. It doesn't give the possibiity to recognize jobs in other states (INPUT, ACTIVE etc.) and made this parser not usable in many cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)