You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2006/04/05 20:36:16 UTC

DO NOT REPLY [Bug 39109] - [net] MVSFTPEntryParser.java only halfway implemented

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39109>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39109





------- Additional Comments From henrik.sorensen@balcab.ch  2006-04-05 19:36 -------
this is my current comments in my working version of MVSFTPEntryParser.java. 
 
try to read it and let know if it is understandable. 
 
/* 
 * Very brief and imcomplete description of the zOS/MVS-filesystem.  
 * (Note: "zOS" is the operating system on the mainframe,  
 *        and is the new name for MVS) 
 *          
 * The filesystem on the mainframe does not have hierarchal structure as  
 * for example the unix filesystem. 
 * For a more comprehensive description, please refer to the IBM manuals 
 * @LINK:www.ibm.... 
 *  
 * Dataset names 
 * ============= 
 *  
 * A dataset name consist of a number of qualifiers separated by '.', 
 * each qualifier can be at most 8 characters, and the total length 
 * of a dataset can be max 44 characters including the dots. 
 *  
 *  
 * Dataset organisation 
 * ==================== 
 *  
 * A dataset represents a piece of storage allocated on one or more disks.  
 * The structure of the storage is described with the field dataset  
organinsation (DSORG). 
 * There are a number of dataset organisations, but only two are usable for FTP 
transfer. 
 *  
 * DSORG: 
 * PS: sequential, or flat file 
 * PO: partitioned dataset 
 * PO-E: extended partitioned dataset 
 *  
 * The PS file is just a flat file, as you would find it on the unix 
 * file system. 
 *  
 * The PO and PO-E files, can be compared to a single level directory  
structure. 
 * A PO file consist of a number of dataset members, or files if you 
 * will. It is possible to CD into the file, and to retrieve the  
 * individual members. 
 *  
 *  
 * Dataset record format 
 * ===================== 
 *  
 * The physical layout of the dataset is described on the dataset itself. 
 * There are a number of record formats (RECFM), but just a few is relavant for  
 * the FTP transfer. 
 *  
 * Any one beginning with either F or V can safely used by FTP transfer. 
 * All others should only be used with great care. 
 * F means a fixed number of records per allocated storage, and V means a 
variable  
 * number of records. 
 *  
 *  
 * Other notes 
 * =========== 
 * 
 * The file system supports automatically backup and retrieval of datasets. If 
a 
 * file is backed up, the ftp LIST command will return: 
 * ARCIVE Not Direct Access Device                KJ.IOP998.ERROR.PL.UNITTEST 
 * 
 * 
 * Implementation notes 
 * ==================== 
 * 
 * Only datasets that have dsorg PS, PO or PO-E and have recfm  
 * beginning with F or V, is fully parsed. 
 *  
 * The following fields in FTPFile is used: 
 * FTPFile.Rawlisting: Always set. 
 * FTPFile.Type: DIRECTORY_TYPE or FILE_TYPE or UNKNOWN or null 
 * FTPFile.Name: name or null 
 * FTPFile.Timestamp: create time or null 
 *  
 */ 
 
 
 
/* Format of ZOS/MVS file list: 
 *     0    1         2      3    4    5      6     7    8     9  
 * Volume Unit    Referred Ext Used Recfm Lrecl BlkSz Dsorg Dsname 
 * B10142 3390   2006/03/20  2   31  F       80    80  PS  MDI.OKL.WORK 
 * ARCIVE Not Direct Access Device                 KJ.IOP998.ERROR.PL.UNITTEST 
 * B1N231 3390   2006/03/20  1   15  VB     256 27998  PO   PLU 
 * B1N231 3390   2006/03/20  1   15  VB     256 27998  PO-E PLB 
 *  
 */ 
 /* ----------------------------------- 
  * [0] Volume 
  * [1] Unit 
  * [2] Referred 
  * [3] Ext: number of extents 
  * [4] Used 
  * [5] Recfm: Record format 
  * [6] Lrecl: Logical record length 
  * [7] BlkSz: Block size 
  * [8] Dsorg: Dataset organisation. Many exists but only support: PS, PO, PO-E 
  * [9] Dsname: Dataset name 
  *  
  * Note: When volume is ARCIVE, it means the dataset is stored somewhere in 
  *       a tape archive. These entries is currently not supported by this 
  *       parser. A null value is returned. 
  *        
  *  
  */ 
// dsorg last two tokens describe file: 
// 'PS': sequential file 
// 'PO': partioned dataset PDS 
// 'PO-E': PDS Library 
// '  ': unknown, probably archived. 
    
/* 
 * Format of a PDS: 
 *    0         1        2          3        4     5     6      7    8 
 *   Name      VV.MM   Created       Changed      Size  Init   Mod   Id 
 *   TBSHELF   01.03 2002/09/12 2002/10/11 09:37    11    11     0 KIL001 
 *   TBTOOL    01.12 2002/09/12 2004/11/26 19:54    51    28     0 KIL001 
 *  
 */ 
/* 
 * [0] Name 
 * [1] VV.MM: Version . modification 
 * [2] Created: yyyy / MM / dd 
 * [3,4] Changed: yyyy / MM / dd  HH:mm 
 * [5] Size: number of lines 
 * [6] Init: number of lines when first created 
 * [7] Mod: number of modified lines a last save 
 * [8] Id: User id for last update 
 *  
 */ 
 

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org