US20050038830A1 - Distribution of mainframe data in the PC environment - Google Patents

Distribution of mainframe data in the PC environment Download PDF

Info

Publication number
US20050038830A1
US20050038830A1 US10/935,464 US93546404A US2005038830A1 US 20050038830 A1 US20050038830 A1 US 20050038830A1 US 93546404 A US93546404 A US 93546404A US 2005038830 A1 US2005038830 A1 US 2005038830A1
Authority
US
United States
Prior art keywords
site
mainframe
sender
dataset
receiver
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US10/935,464
Inventor
Hyung Lee
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to US10/935,464 priority Critical patent/US20050038830A1/en
Publication of US20050038830A1 publication Critical patent/US20050038830A1/en
Priority to US12/069,571 priority patent/US8868515B2/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Definitions

  • the invention relates to the distribution method of mainframe data using PC-based data media. More specifically, the invention relates to a mainframe program for allowing the file transfer of mainframe sequential datasets and libraries of texts or load modules between a mainframe computer and a PC and between two mainframe computers using floppy diskettes, recordable CD-ROM, Internet world wide web, TCP/IP FTP, and email attachment, thus providing an alternative to magnetic tape reels and tape cartridges, also allowing the PC hard disk to be used as a backup storage of the mainframe libraries, as well as for allowing a mainframe text library which is downloaded to a PC to be edited on a local or remote stand-alone PC workstation.
  • Mainframe computers are becoming less expensive ($100,000/MIPS in 1992 , $2,300/MIPS in 2000 , and $840 in 2002). 70% of all business information resides in mainframe databases. The operation costs of the distributed computing based on mini-computers are high. More than anything else, businesses need machines with enough computative power, a need which mini-computers cannot satisfy. Mainframes will continue to be the main workhorses for big businesses for the foreseeable future.
  • Mainframes have been upgraded by replacing the former “dumb” terminals, such as the IBM 3270s terminals which provided little more than a keyboard and a display screen, with desktop personal computers (PCs). These PCs can also be used as stand-alone computers for text editing, word processing, and other office tasks, when not being used as mainframe terminals.
  • desktop personal computers PCs
  • a PC can connect to a mainframe system with the proper software and proper communication link.
  • a PC terminal connects to and communicates with a mainframe through an IBM Systems Network Architecture(SNA) 3270 protocol emulation software.
  • the PC can operate as a LAN terminal using a LAN server, an SNA gateway, and a 3270 emulation software, e.g., Attachmate Extra Personal ClientTM.
  • the PC can work as a stand-alone mainframe terminal through a Synchronous Data Link Control (SDLC) communication board, a leased-line modem, and a 3270 emulation software, such as Attachmate ExtraTM, 3270 EliteTM, or Dynacomm/EliteTM.
  • SDLC Synchronous Data Link Control
  • an Internet-enabled PC can work as a stand-alone mainframe terminal through a Telnet server which supports TCP/IP application protocol TN3270 clients with TN3270 Telnet SNA 3270 protocol emulation software, such as QWS3270 Plus TN3270 Telnet applicationTM of Jolly Giant Software or E-TermTM for IBM of DCSi.
  • Telnet server which supports TCP/IP application protocol TN3270 clients with TN3270 Telnet SNA 3270 protocol emulation software, such as QWS3270 Plus TN3270 Telnet applicationTM of Jolly Giant Software or E-TermTM for IBM of DCSi.
  • a PC connected to a mainframe with an IBM SNA 3270 protocol emulation software or the TN3270 Telnet software supports file transfers between the mainframe and the PC using the IBM mainframe program “IND$FILE”.
  • An Internet-enabled PC connected to a mainframe FTP server using the TCP/IP file transfer protocol (FTP) also supports the file transfer between the mainframe and the PC.
  • TCP/IP file transfer protocol FTP
  • the three file transfer procedures (Procedures #2-4) between a mainframe and a PC are explained as examples.
  • the first procedure (Procedure #2) is a file transfer during a TSO session using Attachmate Extra SNA 3270 emulation software:
  • the second procedure (Procedure #3) is for an FTP file transfer started from the Attachmate main screen without a TSO session:
  • the third procedure is FTP File Transfer started from MS-DOS prompt screen:
  • the mainframe data stored in a PC can be copied to a PC-related data media repeatedly.
  • Ubiquitous PC usage worldwide and the file transfer capability make it possible to send and receive data between mainframe data centers using PCs.
  • PC-based technologies in exchanging information such as email attachments using SMTP, the Internet world wide web, and FTP send/receive facility, allow data centers to transfer mainframe data using methods which were not previously available.
  • mainframe installations still send their mainframe libraries of texts and program load modules to other data centers using the half-inch thick, 9-track, 1600/6250 BPI, 1,200 foot 8.5-inch diameter or 2,400 foot 10.5-inch diameter round reel tapes created from IBM 3420/3430 Magnetic-Tape Units or 18 -track, 550 foot 38,000 BPI tape cartridges created from IBM 3480 Magnetic-tape Units located in the mainframe computer rooms.
  • IBM proprietary magnetic tape units There have been no alternatives until now.
  • mainframe library There are two main reasons for using magnetic tapes exclusively to deliver a mainframe library.
  • a part or whole of a mainframe library can not be downloaded (file transfer from a mainframe to a PC) as a whole.
  • each member of the mainframe library can only be downloaded individually one at a time. Therefore a mainframe library can not be delivered to other data centers using PC-based data media.
  • libraries are processed only by dataset utility programs developed by IBM. Currently, IBM does not provide the capacity to distribute a mainframe library via PC-related data media.
  • each mainframe record is concatenated to the previous record to create a long thread of string, and stored upon the PC.
  • the uploading process breaks down this long concatenated string of PC data into separate mainframe records.
  • a text file can be downloaded to a PC in text mode with a carriage return (CR, hexadecimal value 0D) and line feed (LF, hexadecimal value 0A) marker appended to the end of each record as a record separator.
  • This file can then be uploaded to a mainframe and reverted to its original form by detecting the CR/LF separator as a marker for the end of each record.
  • any text file or hexadecimal file of fixed length records can be transferred to a PC in binary mode without appending a record end marker, and can be reverted to its original form when uploaded to a mainframe in the same binary mode. This is possible only because the length of all records are the same, and each record can be separated at the same length even without record separators. Text sequential datasets of undefined record format are rarely in use.
  • Mainframe load modules are not of fixed length records, they are of undefined record format and they contain a lot of non-character hexadecimal data. As a result, mainframe load modules can not be reverted to their original form when they are uploaded back to a mainframe. Therefore, currently, mostly text datasets of fixed length records, e.g., usually members of text libraries, are delivered, member by member, to other mainframe data centers using PC-based data media.
  • the mainframe library is a partitioned dataset(PDS) and is equivalent to a PC directory or subdirectory which contains a large number of files as its components.
  • the mainframe library also contains components so called members.
  • a single member of a text or load library is simple to process, but the processing of a library as a whole is not simple.
  • Text library members have fixed length records of 80-bytes long, and are used for storing program source codes, macros, procedures (PROCs), JCL statements, help texts, instructions, manuals, documents, and letters.
  • PROCs program source codes
  • JCL statements JCL statements
  • help texts instructions
  • manuals documents
  • letters letters
  • the mainframe program load module is different from text files.
  • the members of a load module library are all executable program load modules (the output of the IBM linkage editor IEWL, also called a load module, and the equivalent of a PC “program” file with .exe, .com, or .dll extensions).
  • Each member has individual records in it.
  • Each record of a load module contains mostly non-readable, non-character hexadecimals, interspersed with some readable characters.
  • the length of any record can be different from that of any other record.
  • the load library is defined only with the maximum record length (at least 256 bytes, but usually greater than 12,000 bytes, upto 32,760 bytes). Each record can be less than 256 bytes long or longer than 256 bytes, up to 32,760 bytes long.
  • load modules must be transferred to a PC in binary mode due to the fact that it contains hexadecimal data.
  • a single program load module is handled as a sequential dataset of undefined record, format, and it is not of fixed length records.
  • Each record of different length must be separated from the next record by an end marker when downloaded to a PC, similar to the use of CR/LF as mentioned above in the case of the text mode transfer.
  • this end marker can be confused as normal hexadecimal data, and can not be handled correctly when uploaded to a mainframe. So, each record of a load module is concatenated at the end of the previous record without a separating marker when downloading. If this concatenated string of data, which does not possess a record separator, is uploaded to a mainframe in binary mode again, the end of each record can not be determined. Therefore the uploaded file will not have its original form, and will no longer be executable.
  • a new mainframe program, PCFORM converts the content of the whole or a part of any mainframe library of load modules or texts or any sequential dataset of fixed record format, undefined record format or variable record format to a sequential dataset of fixed length records ( FIGS. 17-19 ). These converted data can be subsequently downloaded to a PC and reverted to their original form in the same or another mainframe data center, if uploaded from a PC.
  • This invention makes it possible for software text and load libraries and VSAM and DB2 datasets, which are sequential datasets of undefined record format, to be transferred to another data center. Any libraries or any sequential datasets can be transferred to another data center.
  • This invention allows the mainframe data transfer to be conducted using PC-based data media as an alternative to the conventional magnetic tape reels and tape cartridges.
  • the new program PCFORM can be even distributed by a diskette, a recordable CD-ROM, over the world wide web, via FTP, or as an email attachment, and installed at the user's mainframe without having to use the aforementioned tapes. After the installation of PCFORM, any kind of library can be transported to that data center via any PC data media.
  • the PC-based data media mentioned above to be used in conjunction with this invention can include any of the following: 3.5-inch standard 1.44 MB floppy diskettes, 650-700 MB recordable CD-ROM's, 100 MB or 250 MB ZIP disks, 3.5-inch 120 -Mbytes SuperDisk diskettes, email, Internet Website, TCP/IP FTP or TELNET, and any other PC data media technologies which will be widely used in the future, such as recordable DVD-ROM's.
  • This invention helps mainframe programmers download their mainframe texts and load modules from expensive mainframe disks to cheap and high-capacity PC hard disks. This allows mainframe programmers to use PC hard disk space to store backups of their mainframe work text data and load modules. This avoids the excessive buildup of backup libraries within mainframe disks, as well as the external accumulation of magnetic tapes.
  • mainframe programmers can perform routine text editing work on a stand-alone PC work station, instead of signing on to the mainframe.
  • the copy of the downloaded PC file can be carried to a remote PC, where the mainframe programmer can perform any text editing.
  • the main benefits of this invention are derived from the facts that (1) PCs are ubiquitous, and familiar to most mainframe data center users, (2) most mainframe data centers already have a file transfer facility between their PC terminals and the mainframe, (3) a PC hard disk file of the downloaded mainframe dataset can be used repeatedly, (4) copying from a PC hard disk to PC-based data media is simpler, easier, and faster than creating a mainframe magnetic tape, (5) delivery is easy and simple, (6) emerging CD-ROM, Internet, TCP/IP FTP, and email can be used, (7) PC data media can be a convenient means for the backup storage of a mainframe text library and load library, and (8) a PC, local or remote, can be used as a stand-alone working station for mainframe text editing, especially for program source codes.
  • the sender and the receiver of this portable PC data media must have a file transfer facility between a mainframe and a PC.
  • the program PCFORM can be installed on their mainframe system using the invention itself, without using any magnetic tapes from the start. After the program PCFORM is installed, a part or whole of any library or any sequential dataset can be downloaded to a PC, delivered to other mainframe computer data centers using PC-based data media, and uploaded from a PC in those receiving mainframe data centers.
  • the invention provides a method and apparatus for converting a part or whole of a mainframe software load library or text library or a mainframe sequential dataset of fixed record format, undefined record format or variable record format to a sequential dataset of fixed length records which can be distributed using PC-based data media to other mainframe computer data centers.
  • One embodiment of the invention provides a method and apparatus for reverting a mainframe software libraries and data delivered via PC-based data media to its original form when uploaded to a mainframe computer at the same site or at another site.
  • a further embodiment of the invention provides a method and apparatus for storing mainframe text libraries in a PC hard disk and working at a local or remote stand-alone PC for text editing of mainframe program source codes, macros, JCL streams, procs, manuals, documents, and letters which were downloaded from a mainframe.
  • FIG. 1 is a functional block diagram of the PC data media delivery of a single program load module when the sender has the program PCFORM, but the receiver does not;
  • FIG. 2 is a functional block diagram of the PC data media delivery of a program load library when both the sender and the receiver has the program PCFORM;
  • FIG. 3 is a functional block diagrams of the PC data media delivery of a text library when both the sender and the receiver has the program PCFORM;
  • FIG. 4 is a functional block diagrams of the PC data media delivery of a sequential dataset of fixed record format, undefined record format or variable record format when both the sender and the receiver has the program PCFORM;
  • FIG. 5 shows how this invention can be used with the Internet world wide web download
  • FIG. 6 shows how this invention can be used with the Internet email attachment file
  • FIG. 7 shows how this invention can be used with the TCP/IP FTP protocol
  • FIG. 8 is a functional block diagram of the current conventional magnetic tape delivery
  • FIGS. 9-16 are the block diagrams of the program PCFORM
  • FIG. 17 shows the conversion of an input record with a 4-byes header and division into shorter records
  • FIG. 18 shows the conversion of an input record with the division into shorter records and a 4-byes header for each divided shorter record
  • FIG. 19 shows the conversion of an input record with zero padding at the end of the input data
  • TABLE 1 is the listing of the source codes of the program PCFORM in assembler language.
  • FIGS. 1 to 7 show four different situations within which this invention can be used with the PC-based data media.
  • FIG. 8 shows the flow of events in the conventional magnetic tape delivery method. Before describing the block diagrams ( FIGS. 1-7 ) of this invention, the flow diagram ( FIG. 8 ) of the conventional magnetic tape delivery, is described first.
  • a software company wants to deliver a whole text library, a program load module, and a whole load library 49 of a software package to a customer data center, a receiver 2 , by tape 76 .
  • This explanation assumes that the name of a sender 1 is BSoft Co.
  • the name of the software package to be delivered is assumed to be CPGM.
  • Receiver 2 of this product CPGM will be referred to as C Co.
  • the JCL streams of JCL Lists #1 and #2 explain how the events of FIG. 8 are actually handled in the mainframe data centers.
  • the job control language (JCL) specifies the program name and the required files for the program.
  • JCL streams or statements are entered to the operating system by the SUBMIT TSO command from the TSO/ISPF screen.
  • the OS interprets these JCL statements, brings up the program from the step library or system load library, allocates the requested files, and passes the CPU control to the program.
  • a sender programmer 17 of a sending site 1 starts 71 a JCL stream of JCL List #1.
  • An IBM utility program IEBCOPY 72 copies a whole text library, a program load module, and a whole load library 49 to tapes 76 as the output.
  • a computer operator 69 mounts 73 the blank tape on the tape drive units when prompted by a system console 69 .
  • system console 69 prompts the unloading 77 of tapes 76 .
  • Receiver programmer 28 receives delivered tapes 79 .
  • Receiver programmer 28 checks the volume serial number of tapes 79 and creates a JCL stream of JCL List #2.
  • Receiver programmer at 28 brings received tapes 79 to a computer room 4 and starts 80 a loading JCL streams in JCL List #2 which requests a tape mount 82 , and copies 83 - 84 the content of tapes 79 to destination libraries 58 .
  • the computer operator unloads 85 tapes 79 .
  • the tape delivery method is characterized by the operator interventions 73 , 77 , 82 , 85 , tapes 76 , 79 , two tape control units in two computer rooms 3 , 4 and moving tapes between computer rooms 3 , 4 and programmers' work areas 17 , 28 .
  • FIGS. 1-7 show four different situations within which this invention can be used with the PC-based data media.
  • the floppy diskette is most common PC-based data media.
  • the recordable CD-ROM is easy and simple to use and provides enough capacity for most mainframe data delivery situations. More and more mainframe data centers are in a situation in which they are ready to use the Internet and the TCP/IP FTP as the data transportation media.
  • This invention does not require the involvement of any mainframe computer operators 69 and 70 nor magnetic tape drive units 76 and 79 , as is requireed in the conventional tape delivery method shown in FIG. 8 .
  • This new PC data media delivery method can be used in two different ways: when the receiver with and without the program PCFORM installed.
  • FIG. 1 show the flow of the functional events in Procedure #5 when a sender 1 has a program PCFORM 13 , but a receiver 2 doesn't have it.
  • Sender 1 tries to send a copy of a single program load module 8 to another data center 2 which does not have the mainframe program PCFORM 13 .
  • receiver 1 can handle an individual program load module separately, but cannot handle a whole library of data.
  • a sender programmer at a PC 17 converts single mainframe program load module 8 to a download sequential dataset 16 of fixed record length of 256 bytes.
  • Sender programmer at 17 downloads 18 - 23 the converted content in download sequential dataset 16 to PC 17 hard disk using Procedure #2, #3 or #4.
  • Sender programmer at 17 chooses a PC data media 25 , copies PC 17 hard disk file to a transportation media 25 , and mails 26 it, or notifies receiver 2 that program load module 8 is in a sender's Website 62 or FTP site 65 .
  • a receiver programmer at PC 28 receives 26 a PC data media 27 and stores 29 it in PC 28 hard disk.
  • Receiver programmer at 28 uploads 30 - 35 the received data from PC 28 to a mainframe upload sequential dataset 36 of the same record length, 256 bytes, as used for download sequential dataset 16 at sender 1 .
  • Receiver programmer at 28 converts the content of upload sequential dataset 36 to a member of a destination program load library 46 using an IBM utility program IEBGENER 38 and an IBM linkage editor IEWL 43 .
  • FIGS. 2-4 show the flow of functional events in Procedure #6 when both a sender 1 and a receiver 2 have program PCFORM 48 , 55 .
  • Sender 1 can send a single load module, a part or whole of a load library, a part or whole of a text library or any sequential dataset 49 to receiver 2 .
  • a sender programmer at a PC 17 converts 50 - 51 a whole or part of program load module library, a whole or part of text library or a sequential dataset 49 to a download sequential dataset 52 of fixed length record of 80-bytes long using program PCFORM 48 .
  • Sender programmer at 17 downloads 18 - 23 the content of download sequential dataset 52 to PC 17 hard disk using Procedure #2, #3 or #4.
  • Sender programmer at 17 chooses a PC data transportation media 25 , copies PC 17 hard disk file(s) to transportation media 25 , and mails 26 them or notifies receiver 2 that program load module(s) and/or text(s) are in a sender's Website 62 or FTP Server 65 .
  • a receiver programmer at a PC 28 receives 26 a PC data media 27 and stores 29 them in PC 28 hard disk.
  • Receiver programmer at 28 uploads 30 - 35 the received data from PC 28 hard disk to a mainframe upload sequential dataset 53 of the same record length, 80 bytes, as used for download sequential dataset 52 of sender 1 .
  • Receiver programmer at 28 converts 56 - 57 the content of mainframe upload sequential dataset 53 to a part or whole of a destination program load module library, a part or whole of a destination text library or a destination sequential dataset of respective record format 58 accordingly using program PCFORM 55 .
  • the first three steps are for sender 1 (i.e., a mainframe software vendor company) to create PC 17 hard disk file(s) from a whole or part of program load module library, a whole or part of text library or a sequential dataset 49 of a sender's mainframe system.
  • sender 1 i.e., a mainframe software vendor company
  • receiver 2 i.e., general user mainframe data centers
  • receiver 2 i.e., general user mainframe data centers
  • convert data delivered in PC data media 27 members of mainframe destination load module library or text library or a sequential dataset 58 .
  • program load module library and/or text library 58 already exists in a user data center 4 , only the delivered members of libraries will be added or updated in place.
  • a downloaded mainframe data file in PC 17 hard disk can be copied to a Website 62 and downloaded by authorized mainframe users 28 via the Internet 60 as in FIG. 5 .
  • the program can be sent to each email user 28 directly as an email attachment as in FIG. 6 .
  • receiver programmer 28 can receive the content of sender's mainframe download dataset 16 via TCP/IP FTP as in FIG. 7 .
  • FIG. 1 and FIGS. 2-4 are described in more detail. All blocks, except blocks of TSO File Transfer and IND$FILE, in the figures represent different JCL streams, JCL Lists #3, #4, #6, #7, #9 and #12, which are explained in more detail.
  • FIG. 1 is described first, and then FIGS. 2-4 are explained.
  • FIG. 1 shows the functional block diagram when sender 1 has program PCFORM 13 , but receiver 2 doesn't have the mainframe program PCFORM. In this situation, receiver 2 can only handle a single load module.
  • This diagram explains how to send single program load module 8 to a mainframe user data center 2 via floppy diskettes or recordable CD-ROM 25 , 27 without the involvement of magnetic tapes, and how to install the program into a mainframe destination load library 46 .
  • This diagram also shows how the new program PCFORM can be delivered to other software companies and general mainframe user companies without the need for magnetic tapes at the beginning.
  • the JCL streams assume that the name of sender 1 is ASoft Co., the developer of the program PCFORM.
  • the name of the program to be delivered is assumed to be PCFORM.
  • receiver does not have the program PCFORM.
  • Receiver 2 of this product PCFORM will be referred to as C Co., with a mainframe data center 4 .
  • Program PCFORM 8 is assumed to be in the program library ASOFT.LOADLIB at sender 1 .
  • the delivered PCFORM will be installed in C Co.'s destination load library, C.ASOFT.LOADLIB 46 .
  • FIG. 1 describes the download procedure for sender 1 to create portable floppy diskette or recordable CD-ROM 25 .
  • the first step of creating download sequential dataset 16 is done by use of an IBM linkage editor program IEWL 7 .
  • the maximum record length of input load module PCFORM 8 in the COPYLIB load library is usually very large, e.g., up to 32,760 bytes.
  • the maximum record length of an output temporary load module member 11 in a SYSLMOD temporary load library is defined as 256 bytes as a default: this is the recommended length.
  • the BLKSIZE value of SYSLMOD temporary load library 11 must be 256 bytes or greater. But the BLKSIZE of 256 bytes is recommended.
  • Step 7 converts 9 - 10 original load module PCFORM 8 into new temporary load module 11 of shorter records.
  • IBM linkage editor IEWL 7 performs this conversion when sender programmer 17 enters 6 a JCL stream of JCL List #3 to the operating system.
  • the SYSLIN control information may be adjusted for each program load module 8 and receiver 2 of this program will use this SYSLIN control information when he uploads the program delivered.
  • the first SYSLIN line ENTRY control statement may or may not be required, and can have a different name from that of the program.
  • Output temporary load module TEMPTEMP 11 in the SYSLMOD library is still an executable load module, which means that the length of each record in the module may be different from the length of others.
  • program PCFORM 13 converts 14 - 15 temporary load module TEMPTEMP 11 to download sequential dataset 16 of uniform fixed length records. This conversion is necessary because only uniform fixed length records of a load module can be reverted to the original load module status when they are downloaded to a PC and uploaded to a mainframe back again.
  • the LRECL value of output download sequential dataset 16 specified by OUT ddname must be the same as the BLKSIZE value (256 bytes is recommended and is used as the default) of IN temporary load library 11 created by a JCL stream of JCL List #3.
  • the disk SPACE value of OUT download sequential dataset 16 is approximately the same as the size of original program load module 8 , when the value of its LRECL is near 256 .
  • Original program load module library 8 itself can be used directly as the IN dataset of above JCL stream (JCL List #4). In this case, linkage editor IEWL 7 step which was necessary in the previous case can be eliminated. But because the LRECL value of OUT download sequential dataset 16 must be the same as the BLKSIZE value of the IN dataset, and due to the large BLKSIZE of original load library 8 (e.g., up to 32,760), the LRECL value of OUT download sequential dataset 16 becomes correspondingly very large. Thus the total output size to transfer between a mainframe and a PC, and between two mainframe data centers can be very large. This is not recommended. The smaller the LRECL value of the OUT dataset, the smaller the amount of the data which needs to be transferred. This is why the minimum allowable value, 256 bytes, is recommended as the default value.
  • download sequential dataset 16 is ready to be transferred to a PC.
  • Sender programmer at 17 transfers 18 - 23 the content of mainframe download sequential dataset, DOWNLOAD.WORK, 16 to PC 17 as C: ⁇ pcform.exe in Binary mode using Procedure #2, #3 or #4.
  • a PC data transportation medium 25 e.g., a floppy diskette, A: ⁇ pcform.exe, or a recordable CD-ROM, D: ⁇ pcform.exe.
  • This dataset data can include letters, installation guides, installation JCLs, help information, manuals, and other documents.
  • Sender 1 mails 26 diskette or CD-ROM 25 to receiver data center 2 .
  • a downloaded load module file in PC 17 hard disk can be copied to a Website 62 and downloaded by authorized mainframe users 28 via the Internet 60 as in FIG. 5 .
  • the program can be sent to each email user 28 directly as an email attachment as in FIG. 6 .
  • receiver programmer 28 can receive the content of sender's mainframe download dataset 16 via TCP/IP FTP as in FIG. 7 .
  • FIG. 1 describes the functional event flow at receiver's mainframe site 2 , referred to as the upload procedure for the user data center.
  • Receiver programmer at 28 of mainframe site 2 receives floppy diskettes or CD-ROM 27 mailed 26 from sender 1 and saves 29 the content of diskettes or CD-ROM 27 to the hard disk of PC 28 .
  • Receiver programmer at 28 copies A: ⁇ pcform.exe or D: ⁇ pcform.exe to C: ⁇ ASOFT ⁇ pcform.exe.
  • Receiver programmer at 28 submits a JCL stream in JCL List #5 to the mainframe operating system to create upload sequential dataset 36 , destination program load library 46 , and destination text library 46 which will receive the data delivered.
  • the LRECL value 256 of FILE1 upload sequential dataset 36 must be the same value as the LRECL value (256 bytes recommended and used as the default) of download sequential dataset 16 of sender 1 .
  • the BLKSIZE value 32,760 of FILE2 destination load library 46 is the maximum allowed value, and is the value which is recommended to use for the transfer. This value can be changed to any number equal to 256 bytes or greater.
  • Receive-r programmer at 28 transfers 30 - 35 delivered data in PC 28 , C: ⁇ ASOFT ⁇ pcform.exe, to mainframe upload sequential dataset, UPLOAD.WORK, 36 in Binary mode using Procedures #2, #3 or #4.
  • Receiver programmer at 28 submits 37 a JCL stream in JCL List #6.
  • JCL List #6 then calls IBM dataset utility program IEBGENER 38 and copies 39 - 40 the content of SYSUT1 upload sequential dataset 36 into a temporary member TEMPTEMP 41 of SYSUT2 destination load library 46 .
  • Temporary output member TEMPTEMP 41 of SYSUT2 destination load library is not executable. Its only purpose is to be used as the input for linkage editor IEWL 43 in a next JCL stream of JCL List #7.
  • Receiver programmer at 28 then submits 42 a JCL stream in JCL List #7 which calls IBM utility program linkage editor IEWL and converts 44 - 45 non-executable member TEMPTEMP 41 of COPYLIB library to an executable load module member PCFORM 46 in the SYSLMOD destination load library.
  • JCL List #7 creates an executable final load module member PCFORM 46 , which was delivered in a converted form via diskette or CD-ROM 27 , in SYSLMOD destination load library 46 .
  • This example description illustrates how single load module PCFORM 46 was delivered via floppy diskette or CD-ROM 27 , without having to use conventional magnetic tape 79 , and is installed just using the available IBM utility programs at mainframe user data center 2 , even without the help of the program PCFORM.
  • this invention will now allow a general mainframe user company, e.g., C Co., to receive any library and any sequential datasets from any mainframe software company, using any kind of PC-based data media, without any need whatsoever for the conventional magnetic tapes which are being currently used for such transfers.
  • a general mainframe user company e.g., C Co.
  • FIGS. 2 and 3 diagrams explain how to send and install a whole or part of a load library or a text library of a mainframe software company 1 to a mainframe user data center 2 via floppy diskettes or recordable CD-ROM 25 without the use of magnetic tapes.
  • FIG. 4 diagram show how a mainframe data center 1 send a sequential dataset of fixed record format, undefined record format or variable record format, e.g., copy datasets of VSAM datasets or DB2 datasets, to another mainframe data center using PC-based data media.
  • FIGS. 2 and 3 are explained first and FIG. 4 will be explained later.
  • the JCL streams of this diagram also assumes for the sake of convenience, as in the FIG. 1 explanation, that the name of sender 1 , a mainframe software company, is assumed to be BSoft Co.
  • a client company 2 of BSoft Co. is assumed to be C Co.
  • the name of a mainframe software package 49 to be delivered to C Co. is CPGM.
  • the load modules and related texts of the mainframe software package, CPGM reside in the libraries BSOFT.CPGM.LOADLIB and BSOFT.CPGM.TEXTLIB at BSoft Co. They will be installed into the destination libraries C.CPGM.LOADLIB and C.CPGM.TEXTLIB of C Co.
  • Program PCFORM is assumed in the program library BSOFT.ASOFT.LOADLIB at BSoft Co. and C.ASOFT.LOADLIB at C Co.
  • This example diagram is based on the use of 3.5-inch standard 1.44 MB floppy diskettes 25 and 27 . Using recordable CD-ROM media is simpler than floppy diskettes.
  • Sender programmer at 17 creates a JCL stream in JCL List #8 for creating download sequential dataset 52 of fixed length records.
  • the primary and secondary quantity of CYLinders may be different depending on the size of each target load library or text library to be delivered, and whether a whole or part of the library or just a single member is to be delivered.
  • One cylinder can hold approximately 650 K bytes of data.
  • the SPACE parameter specifies a maximum of 160 cylinders and an approximate maximum of 104 million bytes (equivalent to approximately 7 2400-ft magnetic tape reels). Download sequential dataset 52 is used repeatedly, so SPACE parameter should be allocated a high enough value to fit all the libraries to be sent out.
  • the LRECL value of texts is fixed at 80 bytes. There is no variety and thus no confusion about the LRECL value for a text library. But for program load modules, sender programmer at 17 can choose any fixed LRECL value of 80 or greater for download sequential dataset, DOWNLOAD.WORK, 52 . Receiver programmer at 28 of mainframe site 2 must use this same LRECL value to create upload sequential dataset 53 . In order to avoid any confusion, the LRECL value of download sequential dataset 52 can be fixed at 80-bytes long as a default value for both the program load modules and texts. The LRECL value 80 is strongly recommended. And this default value of 80 bytes length is used in this example explanation. This dataset of 80 bytes record length can be used for both text libraries and load libraries.
  • sender programmer 17 may notify receiver programmer 28 about the BLKSIZE value of original load module library, e.g., BSOFT.CPGM.LOADLIB 49 .
  • Receiver programmer 28 can create destination program load module library 58 with the BLKSIZE value suggested by sender programmer 17 , or greater up to the maximum allowed BLKSIZE value of 32,760 which can receive any BLKSIZE value of original load library 49 .
  • Sender programmer at 17 submits the above IBM dataset utility program IEFBR14 JCL stream (JCL List #8) to create download sequential dataset, DOWNLOAD.WORK 52 .
  • Download sequential dataset 52 and other download work datasets which will be created later will be used repeatedly for each library download. Therefore the full procedure, from the submission 47 of PCFORM program 48 to the completion 23 of the file transfer to a PC, must be done separately for each library whether it is a load library or a text library. A library is downloaded to a PC one library at a time.
  • Sender programmer at 17 creates a JCL stream (JCL List #9) which will bring up program PCFORM 48 from the STEPLIB library.
  • the IN DD statement identifies original text or load library 49 to be delivered.
  • the OUT dataset is download sequential dataset 52 .
  • the DUMP CONTROL command without any member names makes program PCFORM 48 dump 50 - 51 whole records in IN input original text or load library 49 to OUT output download sequential dataset 52 .
  • the CONTROL control command DUMP converts the content of IN original library 49 to OUT download sequential dataset 52 records.
  • the DUMP command starts at column 1 and can be followed by any number of library member names; in this case only the named members will be dumped to download sequential dataset 52 . More than one member list lines can follow the DUMP control command line, but the first column must be blank.
  • DUMP control command without any member names as shown in the above sample JCL stream, will convert the whole content of original library 49 to download sequential dataset 52 records.
  • DUMP JCL1, JCL2, JCL3, HELP1, HELP2, UPLOAD1, Manual1 Manual2 ERRORMSG , VENDOR )
  • the download procedure of a text library will be repeated after the completion of the load library download.
  • Sender programmer at 17 submits 47 above PCFORM program JCL stream (JCL List #9) to dump the software package in original load library 49 to download sequential dataset 52 .
  • output download sequential dataset 52 is too big for a standard 1.44 MB floppy diskette, the records in download sequential dataset 52 must be divided into smaller sequential datasets in order to use 1.44 MB floppy diskettes as the transportation media. This division is necessary only for 1.44 MB floppy diskettes. If a recordable CD-ROM is used, this division is not necessary. Also, if the data is to be transferred over the world wide web or the TCP/IP FTP, this division is not necessary.
  • this division can be done only in the mainframe. But for texts, this division can be done in the mainframe or in a PC with PC word processors or ASCII text editors.
  • One 3.5-inch floppy diskette can deliver 1.4 million bytes or up to approximately 17,000 records of 80-byte length mainframe records. But let's use the number 15,000 as an example for simplicity. If the library to be downloaded is a text library, it is recommended to divide the library into smaller datasets which are easier for PC text editors to handle.
  • DOWNLOAD.WORK, 52 contains more than 15,000 records of 80-byte long, it is necessary to create more than one smaller temporary work sequential datasets, e.g., DOWNLOAD.WORK1 and DOWNLOAD.WORK2, and so on, until the whole library can be divided into approximately 15,000 80-byte records per each smaller dataset.
  • download sequential dataset(s) 52 is ready to be downloaded to a PC.
  • Sender programmer at 17 transfers 18 - 23 mainframe download sequential datasets 52 to the hard disk of PC 17 individually in Binary mode using Procedure #2, #3 or #4:
  • whole original load library 49 is stored in the hard disk of PC 17 . It is ready to be delivered to any client user data center 2 , e.g., including C Co. in this example.
  • the IN dataset of PCFORM program 48 is a text library 49 .
  • Same download sequential dataset 52 is used repeatedly as the OUT dataset. So the previous content of download sequential dataset 52 will be overwritten with new content every time after this step 48 .
  • the content of download sequential dataset 52 can be divided into smaller work datasets, e.g., DOWNLOAD.WORK1, DOWNLOAD.WORK2, DOWNLOAD.WORK3, DOWNLOAD.WORK4, and so on, using the same method as used for the load library above.
  • sender programmer 17 transfers 18 - 23 the mainframe datasets to the hard disk of PC 17 individually in Text mode using Procedure #2, #3 or #4:
  • whole program load library and/or whole text library 49 are stored in the hard disk of PC 17 . They are ready to be delivered to any client user data center 2 , e.g., C Co. in this example.
  • the libraries are copied to 1.44 MB floppy diskettes:
  • This data will be accompanied with letters, installation guides, installation JCLs, help information, manuals, and other documents.
  • sender programmer 17 mails diskettes 25 which were created.
  • downloaded load module and text files in PC 17 hard disk can be copied to a Website 62 and downloaded by authorized mainframe users 28 via the Internet 60 as in FIG. 5 .
  • the files can be sent to each email user 28 directly as an email attachments as in FIG. 6 .
  • receiver programmer 28 can receive the content of sender's mainframe download dataset 16 via TCP/IP FTP as in FIG. 7 .
  • FIGS. 2 and 3 show the upload procedure for each user data center which received the diskettes of a library.
  • Receiver programmer 28 receives 26 floppy diskettes 27 and saves 29 them onto PC 28 hard disk as:
  • Receiver programmer 28 submits a JCL stream in JCL List #11 to create required datasets: destination load library 58 , destination text library 58 , and upload sequential datasets 53 , e.g., UPLOAD.WORK1, UPLOAD.WORK2, UPLOAD.WORK3, and UPLOAD.WORK4, to receive the data delivered.
  • sequential datasets 53 e.g., UPLOAD.WORK1, UPLOAD.WORK2, UPLOAD.WORK3, and UPLOAD.WORK4
  • the LRECL value of upload sequential datasets, UPLOAD.WORKn 53 must be the same value as LRECL value of download sequential dataset, DOWNLOAD.WORK, 52 at sender's site 1 .
  • the LRECL value of 80 bytes is the default value for the sender. But sender 1 may use a different value, so receiver 2 must be careful about this LRECL value.
  • the disk space parameters of destination load library and destination text library 58 must be carefully decided. This space must be sufficient to receive all the data delivered. Usually sender 1 supplies this information. Upload sequential datasets 53 are used repeatedly for each upload of both the text and load library data, so it is recommended to allocate enough space to fit all situations.
  • the BLKSIZE value 32,760 of destination load library, C.CPGM.LOADLIB, 58 is the maximum allowed value, and is recommended and set as the default value. This value can be changed to any value equal to or greater than the BLKSIZE value of original load library 49 at sender 1 , which is usually supplied by sender 1 .
  • the whole upload procedure from the first step 30 of the file transfer step 30 - 35 to the completion of loading 55 the final library, is also performed repeatedly for each individual library delivered.
  • Each library must be uploaded separately individually.
  • Receiver programmer 28 now transfers 30 - 35 PC 28 files of original load library 49 to mainframe upload sequential datasets 53 in binary mode using Procedure #2, #3 or #4.
  • Receiver programmer 28 has to load 56 - 57 all the contents of upload sequential dataset 53 to destination load library 58 by running 54 program PCFORM 55 .
  • a PCFORM program JCL stream in JCL List #12 is submitted 54 and program PCFORM 55 loads 56 - 57 all the data in IN upload sequential datasets 53 to OUT destination program load library 58 .
  • the CONTROL control command LOAD converts the content of upload sequential datasets 53 to the members of destination library 58 .
  • the LOAD command starts at column 1 and can be followed by any number of library member names. More than one member list lines can follow the LOAD control command line, but the first column of the following lines must be blank. In this case, only the named members are picked up from upload sequential datasets 53 and loaded to destination library 58 .
  • the LOAD control command without any member names, as shown as in the above sample JCL stream, will load the whole content of upload sequential datasets 53 to destination library 58 .
  • JCL Note #2 Example of free format LOAD command syntax (1).
  • LOAD text jcl2 source3 Macro4 Source5 ,SOURCE6
  • the upload of a part or whole of a text library also can be done in just the same way.
  • the PC files of delivered text data are transferred 30 - 35 to mainframe upload sequential datasets 53 and the content of upload sequential datasets 53 are loaded 56 - 57 to destination text library 58 by a program PCFORM JCL stream (JCL List #13).
  • Receiver programmer 28 transfers the PC files of original text library 49 to mainframe upload sequential datasets 53 in Text mode using Procedure #2, #3 or #4.
  • Receiver programmer 28 loads 56 - 57 all the transferred content to destination text library 58 by running 54 program PCFORM JCL stream shown in JCL List #13 which is just the same as above load library upload procedure, except for the OUT library name.
  • the IN dataset is upload sequential dataset 53 and OUT dataset is final destination text library 58 .
  • JCL Lists #12 and #13 are similar except the OUT datasets.
  • Any sequential dataset of fixed record format, undefined record format or variable record format can be transferred to another mainframe using PC-based data media and can be reverted to its original form when uploaded, as depicted in FIG. 4 .
  • the events in FIG. 4 can be explained using JCL streams of JCL Lists #14 and #15, which are similar to JCL Lists #9 or #10 and JCL Lists #12 or #13 with only small differences.
  • the IN dataset in JCL stream of JCL List #14 at the sender's site and the OUT dataset in JCL List #15 at the receiver's site are sequential datasets of fixed record format, undefined record format or variable record format respectively.
  • the block size of both IN and OUT sequential datasets must be the same when they are of undefined record format or variable record format.
  • one data center can send any sequential dataset and a part or whole of a load library or a text library using PC-based data transportation media.
  • Any data center can be a sender or a receiver of mainframe data.
  • the receiver does not have the program PCFORM, it can only receive a single load module, but it can not receive a library or other dataset. This feature is useful to send the program PCFORM to other mainframe data centers using PC-based data media.
  • This invention solves the download and upload problems of a single load module, a part or whole of a load module library, a part or whole of a text library and a sequential dataset by converting to a download sequential dataset of fixed record format.
  • Fixed record format means that each record has the same length.
  • a sequential dataset of fixed record format can be downloaded to a PC and uploaded to a mainframe from a PC into its original form.
  • a dataset which is not of fixed record format must be converted to a sequential dataset of fixed record format first to be delivered to another mainframe data center.
  • the download sequential dataset of the sender and the upload sequential dataset of the receiver are defined as a fixed record format and their logical record length must be the same.
  • VSAM datasets and DB2 datasets are of undefined-type record format.
  • VSAM dataset it's not called undefined record format, but it does have undefined record lengths.
  • its maximum record length and average record length are given.
  • average record length is just an average value, not a minimum value.
  • Each record length can be from 1 byte long to the maximum record length defined.
  • FIG. 1 shows that a single load module is delivered when the sender has the program PCFORM, but the receiver does not have the program PCFORM.
  • the load module is an undefined record format dataset.
  • the logical record length of the download dataset of fixed record length is defined with the same value as the blick size of the library in where the single load module is located.
  • Each input load module record of various length is padded with zeroes at the end of input data up to the blick size length as in FIG. 19 and written out to the download sequential dataset. These padded records are uploaded and reverted to its original form in another mainframe using IBM utility programs IEBGENER and IEWL.
  • FIG. 2 shows that a part or whole of a load module library 0.5 is delivered to another mainframe data center when both the sender and the receiver have the program PCFORM.
  • a load module library is of undefined record format. Only its block size is given and the length of one record can be different from other records and unpredictable. These undefined various length records must be converted to a sequential dataset of fixed length records.
  • the conversion of a load module library is handled in two different ways in this invention.
  • First method ( FIG. 17 ) is: each input record is appended at the beginning of each logical record by a 4-bytes header which contains the real length of the undefined record and this record with 4-bytes header is divided into fixed length shorter records of download sequential dataset of fixed record length format.
  • each input record of various length is first divided into shorter records of (the logical record length of the download sequential dataset minus 4 ) bytes length. Each divided record is appended at the beginning with a 4-bytes of header of 2-bytes of real data length and 2-bytes of sequence number of shorter records in the original input record.
  • the first devided shorter record has the sequence number, 1.
  • the last shorter record of each input record may have the data length shorter than the record length of the download sequential dataset of fixed record format.
  • FIG. 3 shows when a part or whole of a text library is delivered to another mainframe data center when both the sender and receiver have the program PCFORM.
  • a text library all records are of fixed length and their length is 80-bytes long. No conversion is necessary because the output download sequential dataset is of fixed record format and its record length is defined as 80-bytes long. Each record from the input text library is written out to the output download dataset. Upload sequential dataset is also of fixed record format and record length is 80-bytes. Each upload record is written out to the destination text library. There is no conversion of text records.
  • FIG. 4 shows when a sequential dataset of fixed record format, undefined record format or variable record format is delivered to another mainframe data center when both the sender and the receiver have the program PCFORM.
  • a sequential dataset of undefined record format only the maximum record length is known, minimum record length can be 1 byte long and each record can have different record length. This is just the same situation as for the load module library. So, the udefined various length records are converted just the same ways as for the load module library records. The above two conversion methods of a load module library can be used for this sequential dataset of undefined record format.

Abstract

A method of distributing mainframe software and data using PC-based data media is disclosed, comprising a mainframe program for converting a mainframe sequential dataset or all or part of a mainframe library of texts or load modules to a sequential dataset of fixed length records and for reverting these converted records to its original form in the same or another mainframe data center, and procedures for downloading the converted mainframe data to a PC and uploading the PC file to a mainframe. The converted mainframe data downloaded to a PC can be delivered to another mainframe data center using floppy diskketes, recordable CD-ROM, Internet Website, TCP/IP FTP, or email attachment, as an alternative to magnetic tapes. The PC hard disk is used as a backup storage of the mainframe libraries, and a mainframe text library downloaded to a PC can be edited on a local or remote stand-alone PC.

Description

    FIELD OF THE INVENTION
  • The invention relates to the distribution method of mainframe data using PC-based data media. More specifically, the invention relates to a mainframe program for allowing the file transfer of mainframe sequential datasets and libraries of texts or load modules between a mainframe computer and a PC and between two mainframe computers using floppy diskettes, recordable CD-ROM, Internet world wide web, TCP/IP FTP, and email attachment, thus providing an alternative to magnetic tape reels and tape cartridges, also allowing the PC hard disk to be used as a backup storage of the mainframe libraries, as well as for allowing a mainframe text library which is downloaded to a PC to be edited on a local or remote stand-alone PC workstation.
    • DISCUSSION OF RELATED ART
  • There are currently more than 21,000 mainframe data centers worldwide. More than 2 trillion dollars has been invested in mainframe software (around 150 billion lines of COBOL code alone worldwide). Mainframe computers are becoming less expensive ($100,000/MIPS in 1992, $2,300/MIPS in 2000, and $840 in 2002). 70% of all business information resides in mainframe databases. The operation costs of the distributed computing based on mini-computers are high. More than anything else, businesses need machines with enough computative power, a need which mini-computers cannot satisfy. Mainframes will continue to be the main workhorses for big businesses for the foreseeable future.
  • Mainframes have been upgraded by replacing the former “dumb” terminals, such as the IBM 3270s terminals which provided little more than a keyboard and a display screen, with desktop personal computers (PCs). These PCs can also be used as stand-alone computers for text editing, word processing, and other office tasks, when not being used as mainframe terminals.
  • A PC can connect to a mainframe system with the proper software and proper communication link. A PC terminal connects to and communicates with a mainframe through an IBM Systems Network Architecture(SNA) 3270 protocol emulation software. The PC can operate as a LAN terminal using a LAN server, an SNA gateway, and a 3270 emulation software, e.g., Attachmate Extra Personal Client™. The PC can work as a stand-alone mainframe terminal through a Synchronous Data Link Control (SDLC) communication board, a leased-line modem, and a 3270 emulation software, such as Attachmate Extra™, 3270 Elite™, or Dynacomm/Elite™. Or an Internet-enabled PC can work as a stand-alone mainframe terminal through a Telnet server which supports TCP/IP application protocol TN3270 clients with TN3270 Telnet SNA 3270 protocol emulation software, such as QWS3270 Plus TN3270 Telnet application™ of Jolly Giant Software or E-Term™ for IBM of DCSi.
  • The following procedure (Procedure #1) is a PC-mainframe connection procedure for an Internet-enabled PC with QWS3270 Plus TN3270 application software of Jolly Giant Software:
    • Procedure #1
  • A PC-to-Mainframe Connect Using TN3270 Telnet
      • 1. Start the program QWS3270.
      • 2. ‘QWS3270PLUS TN3270 Telnet’ screen comes up.
      •  Click the Host menu.
      • 3. Click Connect from the drop-down list.
      • 4. ‘Host Selection’ screen comes up.
      •  Type Session_Name.e.g., lj01 decided by Host site
      •  Type Host_Name. e.g., 123.45.67.89 a Telnet server's IP address
      •  Type Port number. e.g., 21 or 23. decided by Host site
      •  Choose Terminal Type. e.g., IBM-3278-2
      •  Click Connect button.
      • 5. Internet Dialing and Connecting screens come up.
      • 6. The mainframe data center's main SignOn screen comes up.
      •  Type User Id. e.g., a TSO User ID. lj01
      •  Type Password. e.g., password of ij01
      • 7. TSO screen comes up.
  • A PC connected to a mainframe with an IBM SNA 3270 protocol emulation software or the TN3270 Telnet software supports file transfers between the mainframe and the PC using the IBM mainframe program “IND$FILE”. An Internet-enabled PC connected to a mainframe FTP server using the TCP/IP file transfer protocol (FTP) also supports the file transfer between the mainframe and the PC.
  • The three file transfer procedures (Procedures #2-4) between a mainframe and a PC are explained as examples. The first procedure (Procedure #2) is a file transfer during a TSO session using Attachmate Extra SNA 3270 emulation software:
    • Procedure #2
  • TSO File Transfer With Attachmate Extra Emulator
      • 1. Get out of ISPF screen.
  • 2. On ‘READY’ TSO prompt screen,
      •  click Tools menu.
      • 3. Click Transfer_File from drop-down list.
      • 4. On the ‘Transfer File’ screen:
      •  Type PC_File name.
      •  Type Host_File name inside quotes.
      •  Choose the transfer direction between Send or Receive.
      •  Choose a Scheme between Binary or Text mode.
      •  Choose TSO between the Host Systems TSO, CICS, and CMS.
      •  Click Add_to_List button.
      •  Click Transfer button.
      • 5. ‘File Transfer Progressing’ screen comes up.
      • 6. After the transfer is complete,
      •  the ‘Transfer Summary’ screen appears.
      •  Check for the message ‘TRANS03 File Transfer complete.’
      • 7. Click OK button.
      • 8. A ‘READY’ TSO prompt screen will appear.
  • The second procedure (Procedure #3) is for an FTP file transfer started from the Attachmate main screen without a TSO session:
    • Procedure #3
  • FTP File Transfer From Attachmate Main Screen
      • 1. Terminate TSO session.
      • 2. On Attachmate initial session list screen,
      •  click Tools menu.
      • 3. Click File_Transfer from drop-down list.
      • 4. On ‘File transfer’ screen:
      •  Type PC_File name.
      •  Type Host_File name inside quotes.
      •  Choose the transfer direction between Send or Receive.
      •  Choose a Scheme between Binary or Text mode.
      •  Click Transfer button.
      • 5. On ‘FTP Connect’ screen:
      •  Type Host_IP address. e.g., 123.45.67.89 or alias of FTP server
      •  Type User_ID. e.g., a TSO User ID, lj01
      •  Type Password. e.g., a TSO User ID's password
        • Click OK button.
      • 6. ‘File transfer’ screen comes up.
      • 7. On ‘Transfer Summary’ screen,
      •  check ‘Transferred successfully’ Comment message.
      •  Click OK button.
      • 8. Attachmate initial session list screen comes up.
  • The third procedure (Procedure #4) is FTP File Transfer started from MS-DOS prompt screen:
    • Procedure #4
  • FTP File Transfer From MS-DOS Screen
      • 1. Minimize or terminate all other applications including Attachmate Extra.
      • 2. Start MS-DOS.
      • 3. On MS-DOS screen with C:\WINDOWS>prompt:
      •  Type FTP after C:\WINDOWS>prompt.
      •  Press Enter key.
      • 4. FTP> prompt comes up.
      •  Type OPEN and Host_IP-address at FTP> prompt. e.g., OPEN 123.45.67.89 or OPEN abc.def.ghij.com.
      •  Press Enter key.
      • 5. Internet connection starts,
      •  Dialing screen and Connecting screens come up.
      •  And finally the Internet screen disappears.
      • 6. Click the minimized FTP program icon.
      • 7. MS-DOS screen appears again with FTP messages of
      •  “Connected” and others.
      •  Type User ID at User prompt. e.g., lj01
      •  Press Enter key.
      •  Type password at Password prompt
      •  Press Enter key.
      • 8. “Logon successful” FTP message comes up with FTP>prompt.
      •  Type BINARY or ASCII at FTP> prompt.
      •  At the FTP> prompt,
      •  type GET ‘LJ01.TEXT.LIB(TEXT1)° C.:\LJ01\TEXT1.TXT for download from mainframe to PC or
      •  type PUT C:\LJ01\TEXT1.TXT’LJ01.TE\XT.TEMP1′ for upload from PC to mainframe.
      •  Press Enter key
      • 9. Transfer starts.
      • 10. After completion of transfer,
      •  check for ‘250 Transfer completed successfully’ FTP message.
      • 11. Type QUIT at FTP>prompt.
      •  Press Enter key.
      • 12. Main Windows screen with all icons comes up.
      •  Click the minimized MS-DOS icon.
      • 13. MS-DOS screen comes up again with C:\WINDOWS>prompt.
      •  Type EXIT at C:\WINDOWS> prompt.
      •  Press Enter key.
      • 14. Origïnal Windows screen with all icons comes up.
  • After the mainframe file is transferred to a PC, the mainframe data stored in a PC can be copied to a PC-related data media repeatedly. Ubiquitous PC usage worldwide and the file transfer capability make it possible to send and receive data between mainframe data centers using PCs. Furthermore, the rise of PC-based technologies in exchanging information, such as email attachments using SMTP, the Internet world wide web, and FTP send/receive facility, allow data centers to transfer mainframe data using methods which were not previously available.
  • However, mainframe installations still send their mainframe libraries of texts and program load modules to other data centers using the half-inch thick, 9-track, 1600/6250 BPI, 1,200 foot 8.5-inch diameter or 2,400 foot 10.5-inch diameter round reel tapes created from IBM 3420/3430 Magnetic-Tape Units or 18 -track, 550 foot 38,000 BPI tape cartridges created from IBM 3480 Magnetic-tape Units located in the mainframe computer rooms. There have been no alternatives until now. These magnetic tapes or cartridges require IBM proprietary magnetic tape units.
  • There are two main reasons for using magnetic tapes exclusively to deliver a mainframe library. First, a part or whole of a mainframe library can not be downloaded (file transfer from a mainframe to a PC) as a whole. Currently, each member of the mainframe library can only be downloaded individually one at a time. Therefore a mainframe library can not be delivered to other data centers using PC-based data media. At mainframe data centers, libraries are processed only by dataset utility programs developed by IBM. Currently, IBM does not provide the capacity to distribute a mainframe library via PC-related data media.
  • Second, only sequential datasets of fixed length records (a “flat” file, in PC terms) or text datasets of undefined record format can be delivered to another data center using PC-related data media, and be safely reverted to its original form at another mainframe data center. While any sequential datasets can be downloaded to a PC a single file at a time, not all sequential datasets can be reverted to their original form when uploaded (file transfer from a PC to a mainframe) at the same or another data center.
  • During the downloading process each mainframe record is concatenated to the previous record to create a long thread of string, and stored upon the PC. The uploading process breaks down this long concatenated string of PC data into separate mainframe records. A text file can be downloaded to a PC in text mode with a carriage return (CR, hexadecimal value 0D) and line feed (LF, hexadecimal value 0A) marker appended to the end of each record as a record separator. This file can then be uploaded to a mainframe and reverted to its original form by detecting the CR/LF separator as a marker for the end of each record.
  • In general, any text file or hexadecimal file of fixed length records can be transferred to a PC in binary mode without appending a record end marker, and can be reverted to its original form when uploaded to a mainframe in the same binary mode. This is possible only because the length of all records are the same, and each record can be separated at the same length even without record separators. Text sequential datasets of undefined record format are rarely in use.
  • Mainframe load modules are not of fixed length records, they are of undefined record format and they contain a lot of non-character hexadecimal data. As a result, mainframe load modules can not be reverted to their original form when they are uploaded back to a mainframe. Therefore, currently, mostly text datasets of fixed length records, e.g., usually members of text libraries, are delivered, member by member, to other mainframe data centers using PC-based data media.
  • The mainframe library is a partitioned dataset(PDS) and is equivalent to a PC directory or subdirectory which contains a large number of files as its components. The mainframe library also contains components so called members. There are only two types of mainframe libraries, a text library with only text members and a load library with only program load module members. Each member has records in it. Members of a library have common attributes, such as the record format, maximum record length, and length of each record. Each member can be handled as a separate sequential dataset. A single member of a text or load library is simple to process, but the processing of a library as a whole is not simple.
  • Text library members have fixed length records of 80-bytes long, and are used for storing program source codes, macros, procedures (PROCs), JCL statements, help texts, instructions, manuals, documents, and letters. Currently, only text library members are downloaded to a PC one member at a time, and copies of each text member are delivered using PC-based data media if necessary. A part or whole of a text library is still delivered using conventional magnetic tapes or cartridges exclusively.
  • The mainframe program load module is different from text files. The members of a load module library are all executable program load modules (the output of the IBM linkage editor IEWL, also called a load module, and the equivalent of a PC “program” file with .exe, .com, or .dll extensions). Each member has individual records in it. Each record of a load module contains mostly non-readable, non-character hexadecimals, interspersed with some readable characters. The length of any record can be different from that of any other record. The load library is defined only with the maximum record length (at least 256 bytes, but usually greater than 12,000 bytes, upto 32,760 bytes). Each record can be less than 256 bytes long or longer than 256 bytes, up to 32,760 bytes long.
  • These load modules must be transferred to a PC in binary mode due to the fact that it contains hexadecimal data. A single program load module is handled as a sequential dataset of undefined record, format, and it is not of fixed length records. Each record of different length must be separated from the next record by an end marker when downloaded to a PC, similar to the use of CR/LF as mentioned above in the case of the text mode transfer. However this end marker can be confused as normal hexadecimal data, and can not be handled correctly when uploaded to a mainframe. So, each record of a load module is concatenated at the end of the previous record without a separating marker when downloading. If this concatenated string of data, which does not possess a record separator, is uploaded to a mainframe in binary mode again, the end of each record can not be determined. Therefore the uploaded file will not have its original form, and will no longer be executable.
  • In summary, currently only a sequential dataset of fixed length records (e.g., a member of a text library), can be delivered to other mainframe data centers using PC-related data media. A part or whole library can not be downloaded to a PC as a single unit, so magnetic tapes or cartridges are exclusively used for the distribution of a part or whole of a program load library or text library to other mainframe data centers.
    • SUMMARY OF INVENTION
  • A new mainframe program, PCFORM, converts the content of the whole or a part of any mainframe library of load modules or texts or any sequential dataset of fixed record format, undefined record format or variable record format to a sequential dataset of fixed length records (FIGS. 17-19). These converted data can be subsequently downloaded to a PC and reverted to their original form in the same or another mainframe data center, if uploaded from a PC.
  • This invention makes it possible for software text and load libraries and VSAM and DB2 datasets, which are sequential datasets of undefined record format, to be transferred to another data center. Any libraries or any sequential datasets can be transferred to another data center.
  • This invention allows the mainframe data transfer to be conducted using PC-based data media as an alternative to the conventional magnetic tape reels and tape cartridges. The new program PCFORM can be even distributed by a diskette, a recordable CD-ROM, over the world wide web, via FTP, or as an email attachment, and installed at the user's mainframe without having to use the aforementioned tapes. After the installation of PCFORM, any kind of library can be transported to that data center via any PC data media.
  • The PC-based data media mentioned above to be used in conjunction with this invention can include any of the following: 3.5-inch standard 1.44 MB floppy diskettes, 650-700 MB recordable CD-ROM's, 100 MB or 250 MB ZIP disks, 3.5-inch 120-Mbytes SuperDisk diskettes, email, Internet Website, TCP/IP FTP or TELNET, and any other PC data media technologies which will be widely used in the future, such as recordable DVD-ROM's.
  • This invention helps mainframe programmers download their mainframe texts and load modules from expensive mainframe disks to cheap and high-capacity PC hard disks. This allows mainframe programmers to use PC hard disk space to store backups of their mainframe work text data and load modules. This avoids the excessive buildup of backup libraries within mainframe disks, as well as the external accumulation of magnetic tapes.
  • By downloading the mainframe text library data to a PC, the mainframe programmers can perform routine text editing work on a stand-alone PC work station, instead of signing on to the mainframe. The copy of the downloaded PC file can be carried to a remote PC, where the mainframe programmer can perform any text editing.
  • The main benefits of this invention are derived from the facts that (1) PCs are ubiquitous, and familiar to most mainframe data center users, (2) most mainframe data centers already have a file transfer facility between their PC terminals and the mainframe, (3) a PC hard disk file of the downloaded mainframe dataset can be used repeatedly, (4) copying from a PC hard disk to PC-based data media is simpler, easier, and faster than creating a mainframe magnetic tape, (5) delivery is easy and simple, (6) emerging CD-ROM, Internet, TCP/IP FTP, and email can be used, (7) PC data media can be a convenient means for the backup storage of a mainframe text library and load library, and (8) a PC, local or remote, can be used as a stand-alone working station for mainframe text editing, especially for program source codes.
  • The only requirement to be able to use this invention is that the sender and the receiver of this portable PC data media must have a file transfer facility between a mainframe and a PC. Then the program PCFORM can be installed on their mainframe system using the invention itself, without using any magnetic tapes from the start. After the program PCFORM is installed, a part or whole of any library or any sequential dataset can be downloaded to a PC, delivered to other mainframe computer data centers using PC-based data media, and uploaded from a PC in those receiving mainframe data centers.
  • There has been a need to better integrate emerging PC technology with mainframe technology, and to use the more convenient and cost effective PC-environment data transportation media in mainframe software libraries and data distribution. Also, there was a need to use cheap and high-capacity PC hard disks for storing mainframe text libraries, and use the PC as a stand-alone text editing work station for mainframe text library data in the PC hard disk.
  • The invention provides a method and apparatus for converting a part or whole of a mainframe software load library or text library or a mainframe sequential dataset of fixed record format, undefined record format or variable record format to a sequential dataset of fixed length records which can be distributed using PC-based data media to other mainframe computer data centers.
  • One embodiment of the invention provides a method and apparatus for reverting a mainframe software libraries and data delivered via PC-based data media to its original form when uploaded to a mainframe computer at the same site or at another site.
  • A further embodiment of the invention provides a method and apparatus for storing mainframe text libraries in a PC hard disk and working at a local or remote stand-alone PC for text editing of mainframe program source codes, macros, JCL streams, procs, manuals, documents, and letters which were downloaded from a mainframe.
    • BRIEF DESCRIPTION OF THE DRAWINGS
  • The invention and its particular features and advantages will become more apparent with examination of the following detailed description considered with the accompanying drawings, wherein:
  • FIG. 1 is a functional block diagram of the PC data media delivery of a single program load module when the sender has the program PCFORM, but the receiver does not;
  • FIG. 2 is a functional block diagram of the PC data media delivery of a program load library when both the sender and the receiver has the program PCFORM;
  • FIG. 3 is a functional block diagrams of the PC data media delivery of a text library when both the sender and the receiver has the program PCFORM;
  • FIG. 4 is a functional block diagrams of the PC data media delivery of a sequential dataset of fixed record format, undefined record format or variable record format when both the sender and the receiver has the program PCFORM;
  • FIG. 5 shows how this invention can be used with the Internet world wide web download;
  • FIG. 6 shows how this invention can be used with the Internet email attachment file;
  • FIG. 7 shows how this invention can be used with the TCP/IP FTP protocol;
  • FIG. 8 is a functional block diagram of the current conventional magnetic tape delivery;
  • FIGS. 9-16 are the block diagrams of the program PCFORM;
  • FIG. 17 shows the conversion of an input record with a 4-byes header and division into shorter records;
  • FIG. 18 shows the conversion of an input record with the division into shorter records and a 4-byes header for each divided shorter record;
  • FIG. 19 shows the conversion of an input record with zero padding at the end of the input data; and
  • TABLE 1 is the listing of the source codes of the program PCFORM in assembler language.
    • DETAILED DESCRIPTION OF THE INVENTION
  • FIGS. 1 to 7 show four different situations within which this invention can be used with the PC-based data media. FIG. 8 shows the flow of events in the conventional magnetic tape delivery method. Before describing the block diagrams (FIGS. 1-7) of this invention, the flow diagram (FIG. 8) of the conventional magnetic tape delivery, is described first.
  • Conventional Delivery Using Magnetic Tapes
  • As an example explanation, let's assume that a software company, a sender 1, wants to deliver a whole text library, a program load module, and a whole load library 49 of a software package to a customer data center, a receiver 2, by tape 76. This explanation assumes that the name of a sender 1 is BSoft Co. The name of the software package to be delivered is assumed to be CPGM. Receiver 2 of this product CPGM will be referred to as C Co. The JCL streams of JCL Lists #1 and #2 explain how the events of FIG. 8 are actually handled in the mainframe data centers. The job control language (JCL) specifies the program name and the required files for the program. JCL streams or statements are entered to the operating system by the SUBMIT TSO command from the TSO/ISPF screen. The OS interprets these JCL statements, brings up the program from the step library or system load library, allocates the requested files, and passes the CPU control to the program.
  • A sender programmer 17 of a sending site 1 starts 71 a JCL stream of JCL List #1. An IBM utility program IEBCOPY 72 copies a whole text library, a program load module, and a whole load library 49 to tapes 76 as the output. A computer operator 69 mounts 73 the blank tape on the tape drive units when prompted by a system console 69. After IEBCOPY 72 finishes copying 74-75, system console 69 prompts the unloading 77 of tapes 76.
    JCL List #1
    Copy a text library, a load module
    and a load library to magnetic tape
    //jobname JOB (account),MSGCLASS=V,CLASS=L
    //TEXTS EXEC PGM=IEBCOPY
    //IN DD DISP=SHR,DSN=BSOFT.CPGM.TEXTLIB
    //OUT DD DSN=TEXTLIB.TAPE,
    // DISP=(,KEEP,DELETE),
    // DCB=(BSOFT.CPGM.TEXTLIB),
    // UNIT=TAPE,
    // LABEL=(1,SL), dataset sequence no=1
    // VOL=(,RETAIN,,2)  maximum 2 tapes
    //SYSUT3 DD UNIT=SYSDA,SPACE=(TRK,(500,20))
    //SYSUT4 DD UNIT=SYSDA,SPACE=(TRK,(500,20))
    //SYSPRINT DD SYSOUT=*
    //SYSIN DD *
    COPY INDD=IN,OUTDD=OUT
    //*
    //LOAD1 EXEC PGM=IEBCOPY
    //IN  DD DISP=SHR,DSN=BSOFT.CPGM.LOADLIB
    //OUT DD DSN=PROGRAM1.TAPE,
    // DISP=(,KEEP,DELETE),
    // DCB=(BSOFT.CPGM.LOADLIB),
    // UNIT=TAPE,
    // LABEL=(2,SL), dataset sequence no=2
    // VOL=(,RETAIN,,,REF=*.TEXTS.OUT)
    //SYSUT3 DD UNIT=SYSDA,SPACE=(TRK,(500,20))
    //SYSUT4 DD UNIT=SYSDA,SPACE=(TRK,(500,20))
    //SYSPRINT DD SYSOUT=*
    //SYSIN DD *
    COPY INDD=IN,OUTDD=OUT
    SELECT MEMBER=(PROGRAM1)
    //*
    //LOADS EXEC PGM=IEBCOPY
    //IN  DD DISP=SHR,DSN=BSOFT.CPGM.LOADLIB
    //OUT DD DSN=LOADLIB.TAPE,
    // DISP=(,KEEP,DELETE),
    // DCB=(BSOFT.CPGM.LOADLIB),
    // UNIT=TAPE,
    // LABEL=(3,SL), dataset sequence no=3
    // VOL=(,RETAIN,,,REF=*.LOAD1.OUT)
    //SYSUT3 DD UNIT=SYSDA,SPACE=(TRK,(500,20))
    //SYSUT4 DD UNIT=SYSDA,SPACE=(TRK,(500,20))
    //SYSPRINT DD SYSOUT=*
    //SYSIN DD *
    COPY INDD=IN,OUTDD=OUT
    //
  • Receiver programmer 28 receives delivered tapes 79. Receiver programmer 28 checks the volume serial number of tapes 79 and creates a JCL stream of JCL List #2. Receiver programmer at 28 brings received tapes 79 to a computer room 4 and starts 80 a loading JCL streams in JCL List #2 which requests a tape mount 82, and copies 83-84 the content of tapes 79 to destination libraries 58. After a load job 81 finishes, the computer operator unloads 85 tapes 79.
    JCL List #2
    Loading a text library, a load module,
    and a load library from magnetic tape
    //jobname JOB (account),MSGCLASS=V,CLASS=L
    //TEXTS EXEC PGM=IEBCOPY
    //IN DD DSN=TEXTLIB.TAPE,
    // DISP=OLD,
    // UNIT=TAPE,
    // LABEL=(1,SL), dataset sequence no=1
    // VOL=(,RETAIN,,,SER=123456)
    //*  destination text library
    //OUT DD DSN=C.CPGM.TEXTLIB,
    // DISP=(,CATLG),
    // DCB=(DSORG=PO,RECFM=FB,
    // LRECL=80,BLKSIZE=8000),
    // UNIT=SYSDA,
    // SPACE=(CYL,(5,2,10)) depending on software
    //SYSUT3 DD UNIT=SYSDA,SPACE=(TRK,(500,20))
    //SYSUT4 DD UNIT=SYSDA,SPACE=(TRK,(500,20))
    //SYSPRINT DD SYSOUT=*
    //SYSIN DD *
    COPY INDD=IN,OUTDD=OUT
    //*
    //LOAD1 EXEC PGM=IEBCOPY
    //IN DD DSN=PROGRAM1.TAPE,
    // DISP=OLD,
    // UNIT=TAPE,
    // LABEL=(2,SL), dataset sequence no=2
    // VOL=(,RETAIN,,,REF=*.TEXTS.IN)
    //*  destination load library
    //OUT DD DSN=C.CPGM.LOADLIB,
    // DISP=(,CATLG),
    // DCB=(DSORG=PO,RECFM=U,BLKSIZE=32760),
    // UNIT=SYSDA,
    // SPACE=(CYL,(20,5,50)) depending on software
    //SYSUT3 DD UNIT=SYSDA,SPACE=(TRK,(500,20))
    //SYSUT4 DD UNIT=SYSDA,SPACE=(TRK,(500,20))
    //SYSPRINT DD SYSOUT=*
    //SYSIN DD *
    COPY INDD=IN,OUTDD=OUT
    //*
    //LOADS EXEC PGM=IEBCOPY
    //IN DD DSN=LOADLIB.TAPE,
    // DISP=OLD,
    // UNIT=TAPE,
    // LABEL=(3,SL), dataset sequence no=3
    // VOL=(REF=*.LOAD1.IN)
    //*  destination load library
    //OUT DD DSN=C.CPGM.LOADLIB,
    // DISP=OLD
    //SYSUT3 DD UNIT=SYSDA,SPACE=(TRK,(500,20))
    //SYSUT4 DD UNIT=SYSDA,SPACE=(TRK,(500,20))
    //SYSPRINT DD SYSOUT=*
    //SYSIN DD *
    COPY INDD=IN,OUTDD=OUT
    //
  • The tape delivery method is characterized by the operator interventions 73, 77, 82, 85, tapes 76, 79, two tape control units in two computer rooms 3, 4 and moving tapes between computer rooms 3, 4 and programmers' work areas 17, 28.
  • Delivery by the Present Invention
  • FIGS. 1-7 show four different situations within which this invention can be used with the PC-based data media. The floppy diskette is most common PC-based data media. The recordable CD-ROM is easy and simple to use and provides enough capacity for most mainframe data delivery situations. More and more mainframe data centers are in a situation in which they are ready to use the Internet and the TCP/IP FTP as the data transportation media. This invention does not require the involvement of any mainframe computer operators 69 and 70 nor magnetic tape drive units 76 and 79, as is requireed in the conventional tape delivery method shown in FIG. 8.
  • This new PC data media delivery method can be used in two different ways: when the receiver with and without the program PCFORM installed.
  • 1. When a Receiver Doesn't Have the Program PCFORM
  • FIG. 1 show the flow of the functional events in Procedure #5 when a sender 1 has a program PCFORM 13, but a receiver 2 doesn't have it. Sender 1 tries to send a copy of a single program load module 8 to another data center 2 which does not have the mainframe program PCFORM 13. In this case, receiver 1 can handle an individual program load module separately, but cannot handle a whole library of data.
    • Procedure #5
  • When the receiver doesn't have the program PCFORM
  • 1. A sender programmer at a PC 17 converts single mainframe program load module 8 to a download sequential dataset 16 of fixed record length of 256 bytes.
  • 2. Sender programmer at 17 downloads 18-23 the converted content in download sequential dataset 16 to PC 17 hard disk using Procedure #2, #3 or #4.
  • 3. Sender programmer at 17 chooses a PC data media 25, copies PC 17 hard disk file to a transportation media 25, and mails 26 it, or notifies receiver 2 that program load module 8 is in a sender's Website 62 or FTP site 65.
  • 4. A receiver programmer at PC 28 receives 26 a PC data media 27 and stores 29 it in PC 28 hard disk.
  • 5. Receiver programmer at 28 uploads 30-35 the received data from PC 28 to a mainframe upload sequential dataset 36 of the same record length, 256 bytes, as used for download sequential dataset 16 at sender 1.
  • 6. Receiver programmer at 28 converts the content of upload sequential dataset 36 to a member of a destination program load library 46 using an IBM utility program IEBGENER 38 and an IBM linkage editor IEWL 43.
  • 2. When the Receiver has the Program PCFORM.
  • FIGS. 2-4 show the flow of functional events in Procedure #6 when both a sender 1 and a receiver 2 have program PCFORM 48, 55. Sender 1 can send a single load module, a part or whole of a load library, a part or whole of a text library or any sequential dataset 49 to receiver 2.
    • Procedure #6
  • When the Receiver has the Program PCFORM
  • 1. A sender programmer at a PC 17 converts 50-51 a whole or part of program load module library, a whole or part of text library or a sequential dataset 49 to a download sequential dataset 52 of fixed length record of 80-bytes long using program PCFORM 48.
  • 2. Sender programmer at 17 downloads 18-23 the content of download sequential dataset 52 to PC 17 hard disk using Procedure #2, #3 or #4.
  • 3. Sender programmer at 17 chooses a PC data transportation media 25, copies PC 17 hard disk file(s) to transportation media 25, and mails 26 them or notifies receiver 2 that program load module(s) and/or text(s) are in a sender's Website 62 or FTP Server 65.
  • 4. A receiver programmer at a PC 28 receives 26 a PC data media 27 and stores 29 them in PC 28 hard disk.
  • 5. Receiver programmer at 28 uploads 30-35 the received data from PC 28 hard disk to a mainframe upload sequential dataset 53 of the same record length, 80 bytes, as used for download sequential dataset 52 of sender 1.
  • 6. Receiver programmer at 28 converts 56-57 the content of mainframe upload sequential dataset 53 to a part or whole of a destination program load module library, a part or whole of a destination text library or a destination sequential dataset of respective record format 58 accordingly using program PCFORM 55.
  • For both above two situations of Procedures #5 and #6, the first three steps are for sender 1 (i.e., a mainframe software vendor company) to create PC 17 hard disk file(s) from a whole or part of program load module library, a whole or part of text library or a sequential dataset 49 of a sender's mainframe system.
  • The last three steps are for receiver 2 (i.e., general user mainframe data centers) to convert data delivered in PC data media 27 to members of mainframe destination load module library or text library or a sequential dataset 58. At step 6, if program load module library and/or text library 58 already exists in a user data center 4, only the delivered members of libraries will be added or updated in place.
  • A downloaded mainframe data file in PC 17 hard disk can be copied to a Website 62 and downloaded by authorized mainframe users 28 via the Internet 60 as in FIG. 5. The program can be sent to each email user 28 directly as an email attachment as in FIG. 6. Or receiver programmer 28 can receive the content of sender's mainframe download dataset 16 via TCP/IP FTP as in FIG. 7.
  • The above two different situations, FIG. 1 and FIGS. 2-4, are described in more detail. All blocks, except blocks of TSO File Transfer and IND$FILE, in the figures represent different JCL streams, JCL Lists #3, #4, #6, #7, #9 and #12, which are explained in more detail. FIG. 1 is described first, and then FIGS. 2-4 are explained.
  • Detail Description of FIG. 1
  • FIG. 1 shows the functional block diagram when sender 1 has program PCFORM 13, but receiver 2 doesn't have the mainframe program PCFORM. In this situation, receiver 2 can only handle a single load module. This diagram explains how to send single program load module 8 to a mainframe user data center 2 via floppy diskettes or recordable CD- ROM 25, 27 without the involvement of magnetic tapes, and how to install the program into a mainframe destination load library 46. This diagram also shows how the new program PCFORM can be delivered to other software companies and general mainframe user companies without the need for magnetic tapes at the beginning.
  • For this example explanation, the JCL streams assume that the name of sender 1 is ASoft Co., the developer of the program PCFORM. The name of the program to be delivered is assumed to be PCFORM. In the example, receiver does not have the program PCFORM. Receiver 2 of this product PCFORM will be referred to as C Co., with a mainframe data center 4. Program PCFORM 8 is assumed to be in the program library ASOFT.LOADLIB at sender 1. The delivered PCFORM will be installed in C Co.'s destination load library, C.ASOFT.LOADLIB 46.
  • Download Procedure of the Sender in FIG. 1
  • The left side of FIG. 1 describes the download procedure for sender 1 to create portable floppy diskette or recordable CD-ROM 25.
  • The first step of creating download sequential dataset 16 is done by use of an IBM linkage editor program IEWL 7. The maximum record length of input load module PCFORM 8 in the COPYLIB load library is usually very large, e.g., up to 32,760 bytes. The maximum record length of an output temporary load module member 11 in a SYSLMOD temporary load library is defined as 256 bytes as a default: this is the recommended length. The BLKSIZE value of SYSLMOD temporary load library 11 must be 256 bytes or greater. But the BLKSIZE of 256 bytes is recommended. Step 7 converts 9-10 original load module PCFORM 8 into new temporary load module 11 of shorter records. IBM linkage editor IEWL 7 performs this conversion when sender programmer 17 enters 6 a JCL stream of JCL List #3 to the operating system.
    JCL List #3
    Creating a temporary load module of shorter length
    //jobname JOB (account),MSGCLASS=V,CLASS=L
    //LKED EXEC PGM=IEWL,PARM=‘MAP,XREF,LET,LIST’
    //SYSPRINT DD SYSOUT=*
    //SYSLOUT DD SYSOUT=*
    //SYSUT1 DD DSN=&&SYSUT1,
    // UNIT=SYSDA,SPACE=(CYL, (2,1))
    //COPYLIB DD DISP=SHR,DSN=ASOFT.LOADLIB
    //SYSLMOD DD DSN=TEMP.LOADLIB,
    // DISP=(,CATLG),
    // DCB=(DSORG=PO,RECFM=U,
    // LRECL=0,BLKSIZE=256)
    // UNIT=SYSDA,SPACE=(CYL,(1,1,3))
    //SYSLIN  DD *
     ENTRY PCFORM
     INCLUDE COPYLIB (PCFORM)
     NAME TEMPTEMP
    //
  • Here, the SYSLIN control information may be adjusted for each program load module 8 and receiver 2 of this program will use this SYSLIN control information when he uploads the program delivered. Depending on the software program, the first SYSLIN line ENTRY control statement may or may not be required, and can have a different name from that of the program.
  • Output temporary load module TEMPTEMP 11 in the SYSLMOD library is still an executable load module, which means that the length of each record in the module may be different from the length of others.
  • At the next step, program PCFORM 13 converts 14-15 temporary load module TEMPTEMP 11 to download sequential dataset 16 of uniform fixed length records. This conversion is necessary because only uniform fixed length records of a load module can be reverted to the original load module status when they are downloaded to a PC and uploaded to a mainframe back again. Program PCFORM 13 is executed by entering 12 a JCL stream of JCL List #4 to the OS/390 by sender programmer at 17:
    JCL List #4
    Creating the revertible sequential
    dataset from the temporary load module
    //jobname JOB (account),MSGCLASS=V,CLASS=L
    //CONVERT EXEC PGM=PCFORM
    //STEPLIB DD DISP=SHR,DSN=ASOFT.LOADLIB
    //IN DD DISP=SHR,DSN=TEMP.LOADLIB(TEMPTEMP)
    //OUT DD DSN=DOWNLOAD.WORK,
    // DISP=(,CATLG),
    // DCB=(DSORG=PS,RECFM=FB,
    // LRECL=256,BLKSIZE=2560),
    // UNIT=SYSDA,SPACE=(CYL,(1,1))
    //CONTROL DD *
    DUMP
    //
  • The LRECL value of output download sequential dataset 16 specified by OUT ddname must be the same as the BLKSIZE value (256 bytes is recommended and is used as the default) of IN temporary load library 11 created by a JCL stream of JCL List #3. The disk SPACE value of OUT download sequential dataset 16 is approximately the same as the size of original program load module 8, when the value of its LRECL is near 256.
  • Original program load module library 8 itself can be used directly as the IN dataset of above JCL stream (JCL List #4). In this case, linkage editor IEWL 7 step which was necessary in the previous case can be eliminated. But because the LRECL value of OUT download sequential dataset 16 must be the same as the BLKSIZE value of the IN dataset, and due to the large BLKSIZE of original load library 8 (e.g., up to 32,760), the LRECL value of OUT download sequential dataset 16 becomes correspondingly very large. Thus the total output size to transfer between a mainframe and a PC, and between two mainframe data centers can be very large. This is not recommended. The smaller the LRECL value of the OUT dataset, the smaller the amount of the data which needs to be transferred. This is why the minimum allowable value, 256 bytes, is recommended as the default value.
  • Now, download sequential dataset 16 is ready to be transferred to a PC.
  • Sender programmer at 17 transfers 18-23 the content of mainframe download sequential dataset, DOWNLOAD.WORK, 16 to PC 17 as C:\pcform.exe in Binary mode using Procedure #2, #3 or #4.
  • Sender programmer at 17 copies 24 C:\pcform.exe, to a PC data transportation medium 25, e.g., a floppy diskette, A:\pcform.exe, or a recordable CD-ROM, D:\pcform.exe.
  • This dataset data can include letters, installation guides, installation JCLs, help information, manuals, and other documents.
  • Sender 1 mails 26 diskette or CD-ROM 25 to receiver data center 2.
  • A downloaded load module file in PC 17 hard disk can be copied to a Website 62 and downloaded by authorized mainframe users 28 via the Internet 60 as in FIG. 5. The program can be sent to each email user 28 directly as an email attachment as in FIG. 6. Or receiver programmer 28 can receive the content of sender's mainframe download dataset 16 via TCP/IP FTP as in FIG. 7.
  • Upload Procedure of the Receiver in FIG. 1
  • The right side of FIG. 1 describes the functional event flow at receiver's mainframe site 2, referred to as the upload procedure for the user data center.
  • Receiver programmer at 28 of mainframe site 2 receives floppy diskettes or CD-ROM 27 mailed 26 from sender 1 and saves 29 the content of diskettes or CD-ROM 27 to the hard disk of PC 28. Receiver programmer at 28 copies A:\pcform.exe or D: \pcform.exe to C: \ASOFT\pcform.exe.
  • Receiver programmer at 28 submits a JCL stream in JCL List #5 to the mainframe operating system to create upload sequential dataset 36, destination program load library 46, and destination text library 46 which will receive the data delivered.
  • The LRECL value 256 of FILE1 upload sequential dataset 36 must be the same value as the LRECL value (256 bytes recommended and used as the default) of download sequential dataset 16 of sender 1.
  • The BLKSIZE value 32,760 of FILE2 destination load library 46 is the maximum allowed value, and is the value which is recommended to use for the transfer. This value can be changed to any number equal to 256 bytes or greater.
    JCL List #5
    Creating the receiving datasets
    //jobname JOB (account),MSGCLASS=V,CLASS=L
    //NEWDS EXEC PGM=IEFBR14
    //FILE1 DD DSN=UPLOAD.WORK,
    // DISP=(,CATLG),
    // DCB=(DSORG=PS,RECFM=FB,
    // LRECL=256,BLKSIZE=2560),
    // UNIT=SYSDA,SPACE=(CYL,(1,1))
    //*  destination load library
    //FILE2 DD DSN=C.ASOFT.LOADLIB,
    // DISP=(,CATLG),
    // DCB=(DSORG=PO,RECFM=U,
    // BLKSIZE=32760),
    // UNIT=SYSDA,
    // SPACE=(CYL,(1,1,5)) depending on software
    //* destination text library
    //FILE3 DD DSN=C.ASOFT.TEXTLIB,
    // DISP=(,CATLG),
    // DCB=(DSORG=PO,RECFM=FB,
    // LRECL=80,BLKSIZE=8000),
    // UNIT=SYSDA,
    // SPACE=(CYL,(5,2,10)) depending on software
    //
  • Receive-r programmer at 28 transfers 30-35 delivered data in PC 28, C:\ASOFT\pcform.exe, to mainframe upload sequential dataset, UPLOAD.WORK, 36 in Binary mode using Procedures #2, #3 or #4.
  • Receiver programmer at 28 submits 37 a JCL stream in JCL List #6. JCL List #6 then calls IBM dataset utility program IEBGENER 38 and copies 39-40 the content of SYSUT1 upload sequential dataset 36 into a temporary member TEMPTEMP 41 of SYSUT2 destination load library 46.
    JCL List #6
    Creating a temporary member in a load library
    //jobname JOB (account),MSGCLASS=V,CLASS=L
    //COPY EXEC PGM=IEBGENER
    //SYSUT1 DD DISP=SHR,DSN=UPLOAD.WORK
    //SYSUT2 DD DISP=SHR,DSN=C.ASOFT.LOADLIB(TEMPTEMP)
    //SYSIN DD DUMMY
    //SYSPRINT DD DUMMY
    //
  • Temporary output member TEMPTEMP 41 of SYSUT2 destination load library is not executable. Its only purpose is to be used as the input for linkage editor IEWL 43 in a next JCL stream of JCL List #7.
  • Receiver programmer at 28 then submits 42 a JCL stream in JCL List #7 which calls IBM utility program linkage editor IEWL and converts 44-45 non-executable member TEMPTEMP 41 of COPYLIB library to an executable load module member PCFORM 46 in the SYSLMOD destination load library.
    JCL List #7
    Creating the executable load module
    member from the temporary member
    //jobname JOB (account),MSGCLASS=V,CLASS=L
    //LKED EXEC PGM=IEWL,PARM=‘MAP,XREF,LET,LIST’
    //SYSPRINT DD SYSOUT=*
    //SYSLOUT DD SYSOUT=*
    //SYSUT1 DD DSN=&&SYSUT1,UNIT=SYSDA,
    // SPACE=(CYL,(1,1))
    //COPYLIB DD DISP=SHR,DSN=C.ASOFT.LOADLIB
    //SYSLMOD DD DISP=SHR,DSN=C.ASOFT.LOADLIB
    //SYSLIN DD *
     ENTRY PCFORM
     INCLUDE COPYLIB(TEMPTEMP)
     NAME PCFORM
    //
  • JCL List #7 creates an executable final load module member PCFORM 46, which was delivered in a converted form via diskette or CD-ROM 27, in SYSLMOD destination load library 46.
  • This example description illustrates how single load module PCFORM 46 was delivered via floppy diskette or CD-ROM 27, without having to use conventional magnetic tape 79, and is installed just using the available IBM utility programs at mainframe user data center 2, even without the help of the program PCFORM.
  • In summary, this invention will now allow a general mainframe user company, e.g., C Co., to receive any library and any sequential datasets from any mainframe software company, using any kind of PC-based data media, without any need whatsoever for the conventional magnetic tapes which are being currently used for such transfers.
  • Detail Description of FIGS. 2 and 3
  • A situation in which both sender 1 and receiver 2 have program PCFORM 48, 55 will now be explained. In this scenario both sender 1 (a software company) and receiver 2 (a general mainframe data center) have installed program PCFORM 48, 55 by the method depicted in FIG. 1, and as explained above.
  • FIGS. 2 and 3 diagrams explain how to send and install a whole or part of a load library or a text library of a mainframe software company 1 to a mainframe user data center 2 via floppy diskettes or recordable CD-ROM 25 without the use of magnetic tapes. FIG. 4 diagram show how a mainframe data center 1 send a sequential dataset of fixed record format, undefined record format or variable record format, e.g., copy datasets of VSAM datasets or DB2 datasets, to another mainframe data center using PC-based data media.
  • FIGS. 2 and 3 are explained first and FIG. 4 will be explained later.
  • The JCL streams of this diagram also assumes for the sake of convenience, as in the FIG. 1 explanation, that the name of sender 1, a mainframe software company, is assumed to be BSoft Co. A client company 2 of BSoft Co. is assumed to be C Co. The name of a mainframe software package 49 to be delivered to C Co. is CPGM. The load modules and related texts of the mainframe software package, CPGM, reside in the libraries BSOFT.CPGM.LOADLIB and BSOFT.CPGM.TEXTLIB at BSoft Co. They will be installed into the destination libraries C.CPGM.LOADLIB and C.CPGM.TEXTLIB of C Co. Program PCFORM is assumed in the program library BSOFT.ASOFT.LOADLIB at BSoft Co. and C.ASOFT.LOADLIB at C Co.
  • This example diagram is based on the use of 3.5-inch standard 1.44 MB floppy diskettes 25 and 27. Using recordable CD-ROM media is simpler than floppy diskettes.
  • Download Procedure of the Sender in FIGS. 2 and 3
  • We will begin by detailing the download procedure for sender 1 to create portable floppy diskettes 25 containing the data to be transferred.
  • Sender programmer at 17 creates a JCL stream in JCL List #8 for creating download sequential dataset 52 of fixed length records.
    JCL List #8
    Creating the download sequential dataset
    //jobname JOB (account),MSGCLASS=V,CLASS=L
    //NEWDS EXEC PGM=IEFBR14
    //FILE1 DD DSN=DOWNLOAD.WORK,
    // DISP=(,CATLG),
    // DCB=(DSORG=PS,RECFM=FB,
    // LRECL=80,BLKSIZE=8000),
    // UNIT=SYSDA,SPACE=(CYL,(10,10))
    //
  • The primary and secondary quantity of CYLinders may be different depending on the size of each target load library or text library to be delivered, and whether a whole or part of the library or just a single member is to be delivered. One cylinder can hold approximately 650 K bytes of data. In the above example the SPACE parameter specifies a maximum of 160 cylinders and an approximate maximum of 104 million bytes (equivalent to approximately 7 2400-ft magnetic tape reels). Download sequential dataset 52 is used repeatedly, so SPACE parameter should be allocated a high enough value to fit all the libraries to be sent out.
  • The LRECL value of texts is fixed at 80 bytes. There is no variety and thus no confusion about the LRECL value for a text library. But for program load modules, sender programmer at 17 can choose any fixed LRECL value of 80 or greater for download sequential dataset, DOWNLOAD.WORK, 52. Receiver programmer at 28 of mainframe site 2 must use this same LRECL value to create upload sequential dataset 53. In order to avoid any confusion, the LRECL value of download sequential dataset 52 can be fixed at 80-bytes long as a default value for both the program load modules and texts. The LRECL value 80 is strongly recommended. And this default value of 80 bytes length is used in this example explanation. This dataset of 80 bytes record length can be used for both text libraries and load libraries.
  • When program load modules are sent out to users, sender programmer 17 may notify receiver programmer 28 about the BLKSIZE value of original load module library, e.g., BSOFT.CPGM.LOADLIB 49. Receiver programmer 28 can create destination program load module library 58 with the BLKSIZE value suggested by sender programmer 17, or greater up to the maximum allowed BLKSIZE value of 32,760 which can receive any BLKSIZE value of original load library 49.
  • Sender programmer at 17 submits the above IBM dataset utility program IEFBR14 JCL stream (JCL List #8) to create download sequential dataset, DOWNLOAD.WORK 52.
  • Download sequential dataset 52 and other download work datasets which will be created later will be used repeatedly for each library download. Therefore the full procedure, from the submission 47 of PCFORM program 48 to the completion 23 of the file transfer to a PC, must be done separately for each library whether it is a load library or a text library. A library is downloaded to a PC one library at a time.
  • Sender programmer at 17 creates a JCL stream (JCL List #9) which will bring up program PCFORM 48 from the STEPLIB library. The IN DD statement identifies original text or load library 49 to be delivered. The OUT dataset is download sequential dataset 52.
    JCL List #9
    Dumping the content of a load library to the download sequential dataset
    //jobname JOB (account),MSGCLASS=V,CLASS=L
    //PCFORM EXEC PGM=PCFORM
    //STEPLIB DD DISP=SHR,DSN=BSOFT.ASOFT.LOADLIB
    //SYSPRINT DD SYSOUT=*
    //*  original library
    //IN DD DISP=SHR,DSN=BSOFT.CPGM.LOADLIB
    //*  download dataset
    //OUT DD DISP=SHR,DSN=DOWNLOAD.WORK
    //CONTROL DD *
    DUMP
    //
  • The DUMP CONTROL command without any member names makes program PCFORM 48 dump 50-51 whole records in IN input original text or load library 49 to OUT output download sequential dataset 52.
  • The CONTROL control command DUMP converts the content of IN original library 49 to OUT download sequential dataset 52 records. The DUMP command starts at column 1 and can be followed by any number of library member names; in this case only the named members will be dumped to download sequential dataset 52. More than one member list lines can follow the DUMP control command line, but the first column must be blank. Using DUMP control command without any member names, as shown in the above sample JCL stream, will convert the whole content of original library 49 to download sequential dataset 52 records.
    JCL Note #1
    Examples of free format DUMP command syntax
    (1). DUMP
    (2). DUMP  PROGRAM1 Program2
    program3,PROGRAM4,
    PROGRAM5  program6,
      PROGRAM7,PROGRAM8
    (3). DUMP
    PROGRAM1 PROGRAM2
    PROGRAM3,  PROGRAM4
    PROGRAM5
     PROGRAM6,PROGRAM7
    (4). DUMP (
     JCL1, JCL2, JCL3, HELP1,
      HELP2, UPLOAD1,
    Manual1
    Manual2
     ERRORMSG  , VENDOR
    )
  • Let's start with the download of load library 49 first.
  • The download procedure of a text library will be repeated after the completion of the load library download.
  • Sender programmer at 17 submits 47 above PCFORM program JCL stream (JCL List #9) to dump the software package in original load library 49 to download sequential dataset 52.
  • If output download sequential dataset 52 is too big for a standard 1.44 MB floppy diskette, the records in download sequential dataset 52 must be divided into smaller sequential datasets in order to use 1.44 MB floppy diskettes as the transportation media. This division is necessary only for 1.44 MB floppy diskettes. If a recordable CD-ROM is used, this division is not necessary. Also, if the data is to be transferred over the world wide web or the TCP/IP FTP, this division is not necessary.
  • If a text member or a part or whole of a text library is downloaded to a PC, sometimes it can be edited in the PC using a PC word processor or an ASCII editor. Therefore it is handy to keep the text file small enough to edit in the PC using ASCII editor. Some ASCII editors can not handle larger files.
  • For load modules, this division can be done only in the mainframe. But for texts, this division can be done in the mainframe or in a PC with PC word processors or ASCII text editors.
  • One 3.5-inch floppy diskette can deliver 1.4 million bytes or up to approximately 17,000 records of 80-byte length mainframe records. But let's use the number 15,000 as an example for simplicity. If the library to be downloaded is a text library, it is recommended to divide the library into smaller datasets which are easier for PC text editors to handle.
  • If download sequential dataset, DOWNLOAD.WORK, 52 contains more than 15,000 records of 80-byte long, it is necessary to create more than one smaller temporary work sequential datasets, e.g., DOWNLOAD.WORK1 and DOWNLOAD.WORK2, and so on, until the whole library can be divided into approximately 15,000 80-byte records per each smaller dataset. These temporary smaller datasets are created using the same DCB parameters as download sequential dataset 52, that is, DSORG=PS, RECFM=FB, LRECL=80, BLKSIZE=8000, but with a different SPACE parameter, SPACE=(CYL, (1,1)) for example.
  • And sender programmer at 17 divides the content of download sequential dataset, DOWNLOAD.WORK, 52 into smaller datasets of 15,000 records for each dataset using the TSO/ISPF EDIT panel or another software program. For an explanation, let's assume that download sequential dataset 52 was divided into four smaller datasets, DOWNLOAD.WORK1, DOWNLOAD.WORK2, DOWNLOAD.WORK3, and DOWNLOAD.WORK4.
  • Now, download sequential dataset(s) 52 is ready to be downloaded to a PC.
  • Sender programmer at 17 transfers 18-23 mainframe download sequential datasets 52 to the hard disk of PC 17 individually in Binary mode using Procedure #2, #3 or #4:
      • 1. if download sequential dataset 52 itself is to be downloaded 18-23, download DOWNLOAD.WORK to the PC file C:\CPGM.exe,
      • or
      • 2. if download sequential dataset was divided into smaller datasets,
      • download DOWNLOAD.WORK1 to C:\CPGM1.exe,
      • download DOWNLOAD.WORK2 to C:\CPGM2.exe,
      • download DOWNLOAD.WORK3 to C:\CPGM3.exe,
      • download DOWNLOAD.WORK4 to C:\CPGM4.exe.
  • Now, whole original load library 49 is stored in the hard disk of PC 17. It is ready to be delivered to any client user data center 2, e.g., including C Co. in this example.
  • Now, let's repeat the full download procedure for text library 49. As mentioned before, the download for each individual library starts with the submission 47 of program PCFORM JCL stream (JCL List #10).
  • This time, the IN dataset of PCFORM program 48 is a text library 49. Same download sequential dataset 52 is used repeatedly as the OUT dataset. So the previous content of download sequential dataset 52 will be overwritten with new content every time after this step 48.
    JCL List #10
    Dumping the content of a text library
    to the download sequential dataset
    //jobname JOB (account),MSGCLASS=V,CLASS=L
    //PCFORM EXEC PGM=PCFORM
    //STEPLIB DD DISP=SHR,DSN=BSOFT.ASOFT.LOADLIB
    //SYSPRINT DD SYSOUT=*
    //*  original library
    //IN DD DISP=SHR,DSN=BSOFT.CPGM.TEXTLIB
    //*  download dataset
    //OUT DD DISP=SHR,DSN=DOWNLOAD.WORK
    //CONTROL DD *
    DUMP
    //
  • After PCFORM program 48 is finished successfully, the content of download sequential dataset 52 can be divided into smaller work datasets, e.g., DOWNLOAD.WORK1, DOWNLOAD.WORK2, DOWNLOAD.WORK3, DOWNLOAD.WORK4, and so on, using the same method as used for the load library above.
  • As the final step of the text library download, sender programmer 17 transfers 18-23 the mainframe datasets to the hard disk of PC 17 individually in Text mode using Procedure #2, #3 or #4:
      • 1. if download sequential dataset 52 itself is to be downloaded, download DOWNLOAD.WORK to the PC file C:\CPGM.txt,
      • or
      • 2. if download sequential dataset 52 was divided into smaller work datasets,
      • download DOWNLOAD.WORK1 to C:\CPGM1.txt,
      • download DOWNLOAD.WORK2 to C:\CPGM2.txt,
      • download DOWNLOAD.WORK3 to C:\CPGM3.txt,
      • download DOWNLOAD.WORK4 to C:\CPGM4.txt.
  • Now, whole program load library and/or whole text library 49 are stored in the hard disk of PC 17. They are ready to be delivered to any client user data center 2, e.g., C Co. in this example.
  • Sender programmer at 17 copies 24 all parts of the downloaded libraries from the hard disk of PC 17 to PC data media 25. In the case of the example below, the libraries are copied to 1.44 MB floppy diskettes:
      • copy C:\CPGM1.exe to A:\CPGM1.exe
      • copy C:\CPGM2.exe to A:\CPGM2.exe
      • copy C:\CPGM3.exe to A:\CPGM3.exe
      • copy C:\CPGM4.exe to A:\CPGM4.exe
      • copy C:\CPGM1.txt to A:\CPGM1.txt
      • copy C:\CPGM2.txt to A:\CPGM2.txt
      • copy C:\CPGM3.txt to A:\CPGM3.txt
      • copy C:\CPGM4.txt to A:\CPGM4.txt
  • This data will be accompanied with letters, installation guides, installation JCLs, help information, manuals, and other documents.
  • Now, sender programmer 17 mails diskettes 25 which were created.
  • As like the explanation of FIG. 1 diagram, downloaded load module and text files in PC 17 hard disk can be copied to a Website 62 and downloaded by authorized mainframe users 28 via the Internet 60 as in FIG. 5. The files can be sent to each email user 28 directly as an email attachments as in FIG. 6. Or !5 receiver programmer 28 can receive the content of sender's mainframe download dataset 16 via TCP/IP FTP as in FIG. 7.
  • Upload Procedure of the Receiver in FIGS. 2 and 3
  • The right side of the FIGS. 2 and 3 show the upload procedure for each user data center which received the diskettes of a library.
  • Receiver programmer 28 receives 26 floppy diskettes 27 and saves 29 them onto PC 28 hard disk as:
      • copy A:\CPGM1.exe to C:\BSOFT\CPGM1.exe
      • copy A:\CPGM2.exe to C:\BSOFT\CPGM2.exe
      • copy A:\CPGM3.exe to C:\BSOFT\CPGM3.exe
      • copy A:\CPGM4.exe to C:\BSOFT\CPGM4.exe
      • copy A:\CPGM1.txt to C:\BSOFT\CPGM1.txt
      • copy A:\CPGM2.txt to C:\BSOFT\CPGM2.txt
      • copy A:\CPGM3.txt to C:\BSOFT\CPGM3.txt
      • copy A:\CPGM4.txt to C:\BSOFT\CPGM4.txt.
  • Receiver programmer 28 submits a JCL stream in JCL List #11 to create required datasets: destination load library 58, destination text library 58, and upload sequential datasets 53, e.g., UPLOAD.WORK1, UPLOAD.WORK2, UPLOAD.WORK3, and UPLOAD.WORK4, to receive the data delivered.
    JCL List #11
    Creating the receiving datasets
    //jobname JOB (account),MSGCLASS=V,CLASS=L
    //NEWDS EXEC PGM=IEFBR14
    //*  destination text library
    //DD1 DD DSN=C.CPGM.TEXTLIB,
    // DISP=(,CATLG),
    // DCB=(DSORG=PO,RECFM=FB,
    // LRECL=80,BLKSIZE=8000),
    // UNIT=SYSDA,
    // SPACE=(CYL,(10,10,20)) depending on software
    //* destination program library
    //DD2 DD DSN=C.CPGM.LOADLIB,
    // DISP=(,CATLG),
    // DCB=(DSORG=PO,RECFM=U,BLKSIZE=32760),
    // UNIT=SYSDA,
    // SPACE=(CYL,(10,10,20)) depending on software
    //DD3 DD DSN=UPLOAD.WORK1,
    // DISP=(,CATLG),
    // DCB=(DSORG=PS,RECFM=FB,
    // LRECL=80,BLKSIZE=800),
    // UNIT=SYSDA,SPACE=(CYL,(1,1))
    //*  for Cpgm2.exe or .txt
    //DD4 DD DSN=UPLOAD.WORK2,
    // DISP=(,CATLG),
    // DCB=(DSORG=PS,RECFM=FB,
    // LRECL=80,BLKSIZE=800),
    // UNIT=SYSDA,SPACE=(CYL,(1,1))
    //*  for Cpgm3.exe or .txt
    //DD5 DD DSN=UPLOAD.WORK3,
    // DISP=(,CATLG),
    // DCB=(DSORG=PS,RECFM=FB,
    // LRECL=80,BLKSIZE=800),
    // UNIT=SYSDA,SPACE=(CYL,(1,1))
    //* for Cpgm4.exe or .txt
    //DD6 DD DSN=UPLOAD.WORK4,
    // DISP=(,CATLG),
    // DCB=(DSORG=PS,RECFM=FB,
    // LRECL=80,BLKSIZE=800),
    // UNIT=SYSDA,SPACE=(CYL,(1,1))
    //
  • The LRECL value of upload sequential datasets, UPLOAD.WORKn 53 must be the same value as LRECL value of download sequential dataset, DOWNLOAD.WORK, 52 at sender's site 1. The LRECL value of 80 bytes is the default value for the sender. But sender 1 may use a different value, so receiver 2 must be careful about this LRECL value.
  • The disk space parameters of destination load library and destination text library 58 must be carefully decided. This space must be sufficient to receive all the data delivered. Mostly sender 1 supplies this information. Upload sequential datasets 53 are used repeatedly for each upload of both the text and load library data, so it is recommended to allocate enough space to fit all situations.
  • At the above, the BLKSIZE value 32,760 of destination load library, C.CPGM.LOADLIB, 58 is the maximum allowed value, and is recommended and set as the default value. This value can be changed to any value equal to or greater than the BLKSIZE value of original load library 49 at sender 1, which is usually supplied by sender 1.
  • Like the download procedure of each library, the whole upload procedure, from the first step 30 of the file transfer step 30-35 to the completion of loading 55 the final library, is also performed repeatedly for each individual library delivered. Each library must be uploaded separately individually.
  • Let's start with the upload of the load library data delivered. The upload procedure for the text library data will be repeated later after the completion of the upload of the load library data.
  • Receiver programmer 28 now transfers 30-35 PC 28 files of original load library 49 to mainframe upload sequential datasets 53 in binary mode using Procedure #2, #3 or #4.
      • transfer C:\BSOFT\CPGM1.exe to UPLOAD.WORK1.
      • transfer C:\BSOFT\CPGM2.exe to UPLOAD.WORK2.
      • transfer C:\BSOFT\CPGM3.exe to UPLOAD.WORK3.
      • transfer C:\BSOFT\CPGM4.exe to UPLOAD.WORK4.
  • Now, all the copies of original load library 49 are transferred to a receiver's mainframe 4.
  • Receiver programmer 28 has to load 56-57 all the contents of upload sequential dataset 53 to destination load library 58 by running 54 program PCFORM 55. A PCFORM program JCL stream in JCL List #12 is submitted 54 and program PCFORM 55 loads 56-57 all the data in IN upload sequential datasets 53 to OUT destination program load library 58.
    JCL List #12
    Loading the delivered load library data to a load library
    //jobname JOB (account),MSGCLASS=V,CLASS=L
    //PCFORM EXEC PGM=PCFORM
    //STEPLIB DD DISP=SHR,DSN=C.ASOFT.LOADLIB
    //SYSPRINT DD SYSOUT=*
    //IN DD DISP=SHR,DSN=UPLOAD.WORK1
    //  DD DISP=SHR,DSN=UPLOAD.WORK2
    //  DD DISP=SHR,DSN=UPLOAD.WORK3
    //  DD DISP=SHR,DSN=UPLOAD.WORK4
    //* destination library
    //OUT DD DISP=SHR,DSN=C.CPGM.LOADLIB
    //CONTROL DD *
    LOAD
    //
  • Here, the CONTROL control command LOAD converts the content of upload sequential datasets 53 to the members of destination library 58. The LOAD command starts at column 1 and can be followed by any number of library member names. More than one member list lines can follow the LOAD control command line, but the first column of the following lines must be blank. In this case, only the named members are picked up from upload sequential datasets 53 and loaded to destination library 58. The LOAD control command without any member names, as shown as in the above sample JCL stream, will load the whole content of upload sequential datasets 53 to destination library 58.
    JCL Note #2
    Example of free format LOAD command syntax
    (1). LOAD
    (2). LOAD  PROGRAM1 PROGRAM2
      PROGRAM3,Program4,
      PROGRAM5  program6,
     PROGRAM7,PROGRAM8
    (3). LOAD
    PROGRAM1 PROGRAM2
     program3,  PROGRAM4
    PROGRAM5
     PROGRAM6,PROGRAM7
    (4). LOAD (
      text jcl2
      source3
      Macro4
    Source5  ,SOURCE6 )
  • Now, delivered original load library or load modules 49 were loaded 56-57 into destination program load module library 58. This was done without the use of magnetic tape.
  • The upload of a part or whole of a text library also can be done in just the same way. At first, the PC files of delivered text data are transferred 30-35 to mainframe upload sequential datasets 53 and the content of upload sequential datasets 53 are loaded 56-57 to destination text library 58 by a program PCFORM JCL stream (JCL List #13).
  • Receiver programmer 28 transfers the PC files of original text library 49 to mainframe upload sequential datasets 53 in Text mode using Procedure #2, #3 or #4.
      • transfer C:\BSOFT\CPGM1.txt to UPLOAD.WORK1.
      • transfer C:\BSOFT\CPGM2.txt to UPLOAD.WORK2.
      • transfer C:\BSOFT\CPGM3.txt to UPLOAD.WORK3.
      • transfer C:\BSOFT\CPGM4.txt to UPLOAD.WORK4.
  • Receiver programmer 28 loads 56-57 all the transferred content to destination text library 58 by running 54 program PCFORM JCL stream shown in JCL List #13 which is just the same as above load library upload procedure, except for the OUT library name. The IN dataset is upload sequential dataset 53 and OUT dataset is final destination text library 58.
    JCL List #13
    Loading the delivered text library data to a text library
    //jobname JOB (account),MSGCLASS=V,CLASS=L
    //PCFORM EXEC PGM=PCFORM
    //STEPLIB DD DISP=SHR,DSN=C.ASOFT.LOADLIB
    //SYSPRINT DD SYSOUT=*
    //IN DD DISP=SHR,DSN=UPLOAD.WORK1
    //  DD DISP=SHR,DSN=UPLOAD.WORK2
    //  DD DISP=SHR,DSN=UPLOAD.WORK3
    //  DD DISP=SHR,DSN=UPLOAD.WORK4
    //* destination text library
    //OUT DD DISP=SHR,DSN=C.CPGM.TEXTLIB
    //CONTROL DD *
    LOAD
    //
  • Text members or a whole text library were loaded 56-57 into destination text library 58. JCL Lists #12 and #13 are similar except the OUT datasets.
  • Delivery of Various Sequential Datasets in FIG. 4
  • Any sequential dataset of fixed record format, undefined record format or variable record format can be transferred to another mainframe using PC-based data media and can be reverted to its original form when uploaded, as depicted in FIG. 4.
  • The events in FIG. 4 can be explained using JCL streams of JCL Lists #14 and #15, which are similar to JCL Lists #9 or #10 and JCL Lists #12 or #13 with only small differences. The IN dataset in JCL stream of JCL List #14 at the sender's site and the OUT dataset in JCL List #15 at the receiver's site are sequential datasets of fixed record format, undefined record format or variable record format respectively. The block size of both IN and OUT sequential datasets must be the same when they are of undefined record format or variable record format. The logical record length of both IN and OUT sequential datasets must be same when they are of fixed record format. Download and upload procedures of FIG. 4 are exactly the same as in FIGS. 2 and 3.
    JCL List #14
    Dumping the content of a sequential
    dataset to the download sequential dataset
    //jobname JOB (account),MSGCLASS=V,CLASS=L
    //PCFORM EXEC PGM=PCFORM
    //STEPLIB DD DISP=SHR,DSN=BSOFT.ASOFT.LOADLIB
    //SYSPRINT DD SYSOUT=*
    //IN DD DISP=SHR,DSN=a_F/U/V_dataset_name
    //OUT DD DISP=SHR,DSN=DOWNLOAD.WORK
    //CONTROL DD *
    DUMP
    //
    JCL List #15
    Loading the delivered data to a destination sequential
    dataset
    //jobname JOB (account),MSGCLASS=V,CLASS=L
    //PCFORM EXEC PGM=PCFORM
    //STEPLIB DD DISP=SHR,DSN=C.ASOFT.ASOFT.LOADLIB
    //SYSPRINT DD SYSOUT=*
    //IN DD DISP=SHR,DSN=UPLOAD.WORK
    //OUT DD DISP=SHR,DSN=a_F/U/V_dataset_name
    //CONTROL DD *
    LOAD
    //

    CONCLUSION of FIGS. 1-7
  • If two mainframe data centers have the program PCFORM, one data center can send any sequential dataset and a part or whole of a load library or a text library using PC-based data transportation media. Any data center can be a sender or a receiver of mainframe data.
  • If the receiver does not have the program PCFORM, it can only receive a single load module, but it can not receive a library or other dataset. This feature is useful to send the program PCFORM to other mainframe data centers using PC-based data media.
  • Creation of Download Sequential Datasets
  • This invention solves the download and upload problems of a single load module, a part or whole of a load module library, a part or whole of a text library and a sequential dataset by converting to a download sequential dataset of fixed record format.
  • Fixed record format means that each record has the same length. As the explanation in the section of the Discussion of Related Art, only a sequential dataset of fixed record format can be downloaded to a PC and uploaded to a mainframe from a PC into its original form. A dataset which is not of fixed record format must be converted to a sequential dataset of fixed record format first to be delivered to another mainframe data center. The download sequential dataset of the sender and the upload sequential dataset of the receiver are defined as a fixed record format and their logical record length must be the same.
  • For undefined record format dataset, only the block size is 0.5 given and each block has only one record in it. So the block size is the maximum length of the records. Minimum record length can be 1 byte long. Each record can have different record length of from 1 byte to the maximum record length defined. This type of dataset cannot be reverted to its original form if downloaded to a PC and uploaded back to a mainframe. This type of dataset must first be converted to a sequential dataset of fixed record format to be delivered to another mainframe data center. A program load module library and its members, program load modules, are of undefined record format.
  • Many VSAM datasets and DB2 datasets are of undefined-type record format. For VSAM dataset, it's not called undefined record format, but it does have undefined record lengths. In many VSAM datasets, its maximum record length and average record length are given. Here, average record length is just an average value, not a minimum value. Each record length can be from 1 byte long to the maximum record length defined. When these VSAM datasets are copied to a sequential dataset, the sequential dataset must be of an undefined record format.
  • FIG. 1 shows that a single load module is delivered when the sender has the program PCFORM, but the receiver does not have the program PCFORM. The load module is an undefined record format dataset. In this case, the logical record length of the download dataset of fixed record length is defined with the same value as the blick size of the library in where the single load module is located. Each input load module record of various length is padded with zeroes at the end of input data up to the blick size length as in FIG. 19 and written out to the download sequential dataset. These padded records are uploaded and reverted to its original form in another mainframe using IBM utility programs IEBGENER and IEWL.
  • FIG. 2 shows that a part or whole of a load module library 0.5 is delivered to another mainframe data center when both the sender and the receiver have the program PCFORM. As explained above, a load module library is of undefined record format. Only its block size is given and the length of one record can be different from other records and unpredictable. These undefined various length records must be converted to a sequential dataset of fixed length records. The conversion of a load module library is handled in two different ways in this invention. First method (FIG. 17) is: each input record is appended at the beginning of each logical record by a 4-bytes header which contains the real length of the undefined record and this record with 4-bytes header is divided into fixed length shorter records of download sequential dataset of fixed record length format. When uploading, the real record length in a 4-bytes header is analyzed first and proper number of following records are concatenated according to this length. The second method (FIG. 18) is: each input record of various length is first divided into shorter records of (the logical record length of the download sequential dataset minus 4) bytes length. Each divided record is appended at the beginning with a 4-bytes of header of 2-bytes of real data length and 2-bytes of sequence number of shorter records in the original input record. The first devided shorter record has the sequence number, 1. The last shorter record of each input record may have the data length shorter than the record length of the download sequential dataset of fixed record format. When upload, the upload record with the sequence number 1 in the header becomes the start of each output record and the real data length is in the header, so the concatenation is possible.
  • FIG. 3 shows when a part or whole of a text library is delivered to another mainframe data center when both the sender and receiver have the program PCFORM. In the case of a text library, all records are of fixed length and their length is 80-bytes long. No conversion is necessary because the output download sequential dataset is of fixed record format and its record length is defined as 80-bytes long. Each record from the input text library is written out to the output download dataset. Upload sequential dataset is also of fixed record format and record length is 80-bytes. Each upload record is written out to the destination text library. There is no conversion of text records.
  • FIG. 4 shows when a sequential dataset of fixed record format, undefined record format or variable record format is delivered to another mainframe data center when both the sender and the receiver have the program PCFORM. As mentioned above, for a sequential dataset of undefined record format, only the maximum record length is known, minimum record length can be 1 byte long and each record can have different record length. This is just the same situation as for the load module library. So, the udefined various length records are converted just the same ways as for the load module library records. The above two conversion methods of a load module library can be used for this sequential dataset of undefined record format.
  • Although the invention has been described with reference to a particular arrangement of events, features, sequences and the like, these are not intended to exhaust all possible arrangements or features, and indeed many other modifications and variations will be ascertainable to those of skill in the art.

Claims (18)

1. A device for distributing a sequential dataset or a library of texts or load modules comprising:
a sender programmer at the sender's site with a file transfer-enabled mainframe terminal for creating required JCL streams, for creating required datasets, for submitting required JCL streams, for creating the download sequential dataset records, for downloading the download sequential dataset to the PC and for creating PC-based data media to send to the receiver's site;
a sequential dataset or a library at the sender's site to be delivered to the receiver's site;
a download sequential dataset at the sender's site, which is of fixed length record format and its logical record length is 80 bytes or greater, for storing the output of the program PCFORM;
a program PCFORM at the sender's site for converting the sequential dataset or\library to the download sequential dataset of fixed length records;
a downloaded PC hard disk file at the sender's site for storing the downloaded content of the mainframe download sequential dataset;
a receiver programmer at the receiver's site with a mainframe PC terminal for receiving the data from the sender, for creating required JCL streams, for creating required datasets, for uploading the received data from the PC to the mainframe, and for submitting required JCL streams;
an upload sequential dataset at the receiver's site, which is of fixed length record format and its logical record length is equal to the logical record length of the download sequential dataset at the sender's site, for storing the data uploaded from a PC at receiver's site;
a destination sequential dataset or library, with the same record format as the record format of the respective dataset at the sender's site, for storing the data from the upload sequential dataset; and
a program PCFORM at the receiver's site for converting the upload sequential dataset records to the destination sequential dataset or library.
2. The PC data media distributing device of claim 1, wherein said the program PCFORM logic can be expanded in various ways to convert any kind of dataset into said the download sequential dataset.
3. The PC data media distributing device of claim 1, wherein said the download sequential dataset at the sender's site can be reverted back to its original form at the sender's mainframe site.
4. The PC data media distributing device of claim 1, wherein, if a copy of said the download sequential dataset from the sender's site is delivered to the receiver's site, it can be reverted to its original form at the receiver's site.
5. The PC data media distributing device of claim 1, wherein said the ownloaded PC hard disk file at the sender's site can be reverted to its original form if it is uploaded back to the sender's mainframe terminal.
6. The PC data media distributing device of claim 1, wherein, if a copy of said the downloaded PC hard disk file at the sender's site is delivered to the receiver's site, it can be reverted to its original form at the receiver's site, if it is uploaded to the receiver's site mainframe.
7. The PC data media distributing device of claim 1, wherein said the downloaded PC hard disk file at sender's site can be delivered to other mainframe data centers using PC-based data media, such as floppy diskettes, recordable CDs, various USB-port disks, ZIP disks, Internet world wide web download, Internet-based email attachment, TCP/IP FTP GET/PUT, and other PC data media available now and in the future, without the use of conventional magnetic tapes or tape cartridges, and can be reverted to its original form at other mainframe data centers.
8. The PC data media distributing device of claim 1, wherein said the downloaded PC hard disk files of any datasets at the sender's site can be used as backups at the sender's site.
9. The PC data media distributing device of claim 1, wherein the logic of said the program PCFORM can be included into other programs and get the same results.
10. A device for distributing a dataset comprising:
a sender programmer at the sender's site with a file transfer-enabled mainframe terminal for creating required JCL streams, for creating required datasets, for submitting required JCL streams, for creating the download sequential dataset records, for downloading the download sequential dataset to the PC and for creating PC-based data media to send to the receiver's site;
a mainframe dataset at the sender's site to be delivered to the receiver's site;
a download sequential dataset at the sender's site, which is of fixed length record format, for storing the output of the program PCFORM;
a program PCFORM at the sender's site for converting the dataset to the download sequential dataset of fixed length records;
a downloaded PC hard disk file at the sender's site for storing the downloaded content of the mainframe download sequential dataset;
a receiver programmer at the receiver's site with a mainframe PC terminal for receiving the data from the sender, for creating required JCL streams, for creating required datasets, for uploading the received data from the PC to the mainframe, and for submitting required JCL streams;
an upload sequential dataset at the receiver's site, which is of fixed length record format and its logical record length is equal to the logical record length of the download sequential dataset at the sender's site, for storing the data uploaded from a PC at receiver's site;
a destination dataset, with the same record format as the dataset at the sender's site, for storing the data from the upload sequential dataset; and
a program PCFORM at the receiver's site for converting the upload sequential dataset records to the destination dataset.
11. The PC data media distributing device of claim 10, wherein said the program PCFORM logic can be expanded in various ways to convert any kind of dataset into said the download sequential dataset.
12. The PC data media distributing device of claim 10, wherein said the download sequential dataset at the sender's site can be reverted back to its original form at the sender's mainframe site.
13. The PC data media distributing device of claim 10, wherein, if a copy of said the download sequential dataset from the sender's site is delivered to the receiver's site, it can be reverted to its original form at the receiver's site.
14. The PC data media distributing device of claim 10, wherein said the downloaded PC hard disk file at the sender's site can be reverted to its original form if it is uploaded back to the sender's mainframe terminal.
15. The PC data media distributing device of claim 10, wherein, if a copy of said the downloaded PC hard disk file at the sender's site is delivered to the receiver's site, it can be reverted to its original form at the receiver's site, if it is uploaded to the receiver's site mainframe.
16. The PC data media distributing device of claim 10, wherein said the downloaded PC hard disk file at sender's site can be delivered to other mainframe data centers using PC-based data media, such as floppy diskettes, recordable CDs, various USB-port disks, ZIP disks, Internet world wide web download, Internet-based email attachment, TCP/IP FTP GET/PUT, and other PC data media available now and in the future, without the use of conventional magnetic tapes or tape cartridges, and can be reverted to its original form at other mainframe data centers.
17. The PC data media distributing device of claim 10, wherein said the downloaded PC hard disk files of any datasets at the sender's site can be used as backups at the sender's site.
18. The PC data media distributing device of claim 10, wherein the logic of said the program PCFORM can be included into other programs and get the same results.
US10/935,464 2000-11-29 2004-09-07 Distribution of mainframe data in the PC environment Abandoned US20050038830A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US10/935,464 US20050038830A1 (en) 2000-11-29 2004-09-07 Distribution of mainframe data in the PC environment
US12/069,571 US8868515B2 (en) 2000-11-29 2008-02-11 Distribution of mainframe data in the PC environment

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09/726,462 US6886160B1 (en) 2000-11-29 2000-11-29 Distribution of mainframe data in the PC environment
US10/935,464 US20050038830A1 (en) 2000-11-29 2004-09-07 Distribution of mainframe data in the PC environment

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09/726,462 Continuation US6886160B1 (en) 2000-11-29 2000-11-29 Distribution of mainframe data in the PC environment

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/069,571 Division US8868515B2 (en) 2000-11-29 2008-02-11 Distribution of mainframe data in the PC environment

Publications (1)

Publication Number Publication Date
US20050038830A1 true US20050038830A1 (en) 2005-02-17

Family

ID=34136885

Family Applications (3)

Application Number Title Priority Date Filing Date
US09/726,462 Expired - Lifetime US6886160B1 (en) 2000-11-29 2000-11-29 Distribution of mainframe data in the PC environment
US10/935,464 Abandoned US20050038830A1 (en) 2000-11-29 2004-09-07 Distribution of mainframe data in the PC environment
US12/069,571 Expired - Lifetime US8868515B2 (en) 2000-11-29 2008-02-11 Distribution of mainframe data in the PC environment

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US09/726,462 Expired - Lifetime US6886160B1 (en) 2000-11-29 2000-11-29 Distribution of mainframe data in the PC environment

Family Applications After (1)

Application Number Title Priority Date Filing Date
US12/069,571 Expired - Lifetime US8868515B2 (en) 2000-11-29 2008-02-11 Distribution of mainframe data in the PC environment

Country Status (1)

Country Link
US (3) US6886160B1 (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080275944A1 (en) * 2007-05-04 2008-11-06 International Business Machines Corporation Transaction-initiated batch processing
US20090157758A1 (en) * 2000-11-29 2009-06-18 Hyung Sup Lee Distribution of mainframe data in the PC environment
US7689905B1 (en) * 2008-11-05 2010-03-30 International Business Machines Corporation Containment of terminal application run-time data for viewing when disconnected from a host server
CN105610957A (en) * 2016-01-07 2016-05-25 中国联合网络通信集团有限公司 Cloud system and data synchronization method thereof
US10754733B2 (en) 2015-07-16 2020-08-25 Gil Peleg System and method for mainframe computers backup and restore
US11061605B1 (en) 2020-01-09 2021-07-13 International Business Machines Corporation Dynamically performing managed file transfer based on policies

Families Citing this family (50)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6748467B2 (en) * 2001-01-30 2004-06-08 Hitachi, Ltd. High speed data transfer between mainframe storage systems
EP1731999B1 (en) * 2005-06-08 2007-06-20 Ubs Ag Mechanism for dynamically registering of files in a batch processing environment
US7577689B1 (en) * 2005-06-15 2009-08-18 Adobe Systems Incorporated Method and system to archive data
US20070226251A1 (en) * 2006-03-24 2007-09-27 Rocket Software, Inc. Method of augmenting and controlling utility program execution for a relational database management system
US8819011B2 (en) * 2008-07-16 2014-08-26 Cleversafe, Inc. Command line interpreter for accessing a data object stored in a distributed storage network
US9317305B2 (en) * 2011-12-29 2016-04-19 Iii Holdings 1, Llc Systems and methods for data brick creation and use
US9274688B2 (en) * 2012-12-14 2016-03-01 Micro Focus (IP) Development Limited Interfacing systems and methods
US10255170B2 (en) * 2016-12-19 2019-04-09 International Business Machines Corporation On-demand codeset converter generation
CN106815056B (en) * 2017-02-17 2020-09-08 银联国际有限公司 Application heat deployment method and device based on JCL framework
US11947489B2 (en) 2017-09-05 2024-04-02 Robin Systems, Inc. Creating snapshots of a storage volume in a distributed storage system
US10846001B2 (en) 2017-11-08 2020-11-24 Robin Systems, Inc. Allocating storage requirements in a distributed storage system
US10782887B2 (en) 2017-11-08 2020-09-22 Robin Systems, Inc. Window-based prority tagging of IOPs in a distributed storage system
US11392363B2 (en) 2018-01-11 2022-07-19 Robin Systems, Inc. Implementing application entrypoints with containers of a bundled application
US11748203B2 (en) 2018-01-11 2023-09-05 Robin Systems, Inc. Multi-role application orchestration in a distributed storage system
US10628235B2 (en) 2018-01-11 2020-04-21 Robin Systems, Inc. Accessing log files of a distributed computing system using a simulated file system
US10896102B2 (en) 2018-01-11 2021-01-19 Robin Systems, Inc. Implementing secure communication in a distributed computing system
US11099937B2 (en) 2018-01-11 2021-08-24 Robin Systems, Inc. Implementing clone snapshots in a distributed storage system
US11582168B2 (en) 2018-01-11 2023-02-14 Robin Systems, Inc. Fenced clone applications
US10642697B2 (en) 2018-01-11 2020-05-05 Robin Systems, Inc. Implementing containers for a stateful application in a distributed computing system
US10846137B2 (en) 2018-01-12 2020-11-24 Robin Systems, Inc. Dynamic adjustment of application resources in a distributed computing system
US10642694B2 (en) 2018-01-12 2020-05-05 Robin Systems, Inc. Monitoring containers in a distributed computing system
US10579364B2 (en) * 2018-01-12 2020-03-03 Robin Systems, Inc. Upgrading bundled applications in a distributed computing system
US10845997B2 (en) 2018-01-12 2020-11-24 Robin Systems, Inc. Job manager for deploying a bundled application
US10976938B2 (en) 2018-07-30 2021-04-13 Robin Systems, Inc. Block map cache
US11023328B2 (en) 2018-07-30 2021-06-01 Robin Systems, Inc. Redo log for append only storage scheme
US10817380B2 (en) 2018-07-31 2020-10-27 Robin Systems, Inc. Implementing affinity and anti-affinity constraints in a bundled application
US10599622B2 (en) 2018-07-31 2020-03-24 Robin Systems, Inc. Implementing storage volumes over multiple tiers
US11036439B2 (en) 2018-10-22 2021-06-15 Robin Systems, Inc. Automated management of bundled applications
US10908848B2 (en) 2018-10-22 2021-02-02 Robin Systems, Inc. Automated management of bundled applications
US10620871B1 (en) 2018-11-15 2020-04-14 Robin Systems, Inc. Storage scheme for a distributed storage system
US11086725B2 (en) 2019-03-25 2021-08-10 Robin Systems, Inc. Orchestration of heterogeneous multi-role applications
US11256434B2 (en) 2019-04-17 2022-02-22 Robin Systems, Inc. Data de-duplication
US10831387B1 (en) 2019-05-02 2020-11-10 Robin Systems, Inc. Snapshot reservations in a distributed storage system
US10877684B2 (en) 2019-05-15 2020-12-29 Robin Systems, Inc. Changing a distributed storage volume from non-replicated to replicated
US11061856B2 (en) 2019-07-03 2021-07-13 Bank Of America Corporation Data ingestion system
US11226847B2 (en) 2019-08-29 2022-01-18 Robin Systems, Inc. Implementing an application manifest in a node-specific manner using an intent-based orchestrator
US11520650B2 (en) 2019-09-05 2022-12-06 Robin Systems, Inc. Performing root cause analysis in a multi-role application
US11249851B2 (en) 2019-09-05 2022-02-15 Robin Systems, Inc. Creating snapshots of a storage volume in a distributed storage system
US11347684B2 (en) 2019-10-04 2022-05-31 Robin Systems, Inc. Rolling back KUBERNETES applications including custom resources
US11113158B2 (en) 2019-10-04 2021-09-07 Robin Systems, Inc. Rolling back kubernetes applications
US11403188B2 (en) 2019-12-04 2022-08-02 Robin Systems, Inc. Operation-level consistency points and rollback
US11108638B1 (en) * 2020-06-08 2021-08-31 Robin Systems, Inc. Health monitoring of automatically deployed and managed network pipelines
US11528186B2 (en) 2020-06-16 2022-12-13 Robin Systems, Inc. Automated initialization of bare metal servers
US11740980B2 (en) 2020-09-22 2023-08-29 Robin Systems, Inc. Managing snapshot metadata following backup
US11803610B2 (en) * 2020-09-24 2023-10-31 Confie Holding II Co. Systems and methods for updating policy profiles
US11743188B2 (en) 2020-10-01 2023-08-29 Robin Systems, Inc. Check-in monitoring for workflows
US11456914B2 (en) 2020-10-07 2022-09-27 Robin Systems, Inc. Implementing affinity and anti-affinity with KUBERNETES
US11271895B1 (en) 2020-10-07 2022-03-08 Robin Systems, Inc. Implementing advanced networking capabilities using helm charts
US11750451B2 (en) 2020-11-04 2023-09-05 Robin Systems, Inc. Batch manager for complex workflows
US11556361B2 (en) 2020-12-09 2023-01-17 Robin Systems, Inc. Monitoring and managing of complex multi-role applications

Citations (52)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4807224A (en) * 1987-08-21 1989-02-21 Naron Steven E Multicast data distribution system and method
US4855900A (en) * 1987-10-28 1989-08-08 Recognition Equipment Incorporated System for transferring data to a mainframe computer
US4893307A (en) * 1988-02-29 1990-01-09 International Business Machines Corporation Method and apparatus for linking SNA terminals to an SNA host over a packet switched communications network
US5438509A (en) * 1991-02-07 1995-08-01 Heffron; Donald J. Transaction processing in a distributed data processing system
US5530848A (en) * 1992-10-15 1996-06-25 The Dow Chemical Company System and method for implementing an interface between an external process and transaction processing system
US5732275A (en) * 1996-01-11 1998-03-24 Apple Computer, Inc. Method and apparatus for managing and automatically updating software programs
US5812864A (en) * 1991-07-09 1998-09-22 International Business Machines Corporation Personal computer/host emulation system for handling host data with personal computer application programs at personal computers
US5937197A (en) * 1996-11-06 1999-08-10 Ncr Corporation Updating of electronic performance support systems by remote parties
US5999740A (en) * 1996-11-08 1999-12-07 International Computers Limited Updating mechanism for software
US6023710A (en) * 1997-12-23 2000-02-08 Microsoft Corporation System and method for long-term administration of archival storage
US6074435A (en) * 1997-10-30 2000-06-13 Telefonakiebolaget Lm Ericsson (Publ) Remote software download with automatic adjustment for data access compatibility
US6115710A (en) * 1989-09-28 2000-09-05 Sterling Software, Inc. Portable and dynamic distributed transaction management method
US6205579B1 (en) * 1996-10-28 2001-03-20 Altera Corporation Method for providing remote software technical support
US6332163B1 (en) * 1999-09-01 2001-12-18 Accenture, Llp Method for providing communication services over a computer network system
US6385654B1 (en) * 1997-10-23 2002-05-07 International Business Machines Corporation File transferring apparatus and method thereof
US6457109B1 (en) * 2000-08-18 2002-09-24 Storage Technology Corporation Method and apparatus for copying data from one storage system to another storage system
US6480834B1 (en) * 1999-11-17 2002-11-12 Serena Software, Inc. Method and apparatus for serving files from a mainframe to one or more clients
US6493871B1 (en) * 1999-09-16 2002-12-10 Microsoft Corporation Method and system for downloading updates for software installation
US6502106B1 (en) * 1999-03-25 2002-12-31 International Business Machines Corporation System, method, and program for accessing secondary storage in a network system
US6513048B1 (en) * 1999-11-17 2003-01-28 Serena Software, Inc. Method and apparatus for access to files stored on a mainframe using a personal computer user interface
US6529976B1 (en) * 1997-04-01 2003-03-04 Hitachi, Ltd. Heterogeneous computer system, heterogeneous input output system and data back-up method for the systems
US6532463B1 (en) * 1998-12-01 2003-03-11 University Of Florida Web page accessing of data bases and mainframes
US6536039B2 (en) * 1998-12-24 2003-03-18 Avaya Technology Corp. Software for seamless interconnectivity between active program modules on integrated arrangement of CD drive, data server, and PC hard disk drive
US6546474B1 (en) * 1999-08-07 2003-04-08 International Business Machines Corporation Method and system for the fast backup and transmission of data
US6571282B1 (en) * 1999-08-31 2003-05-27 Accenture Llp Block-based communication in a communication services patterns environment
US6601212B1 (en) * 2000-03-29 2003-07-29 Hewlett-Packard Development Company, Lp. Method and apparatus for downloading firmware to a non-volatile memory
US6615404B1 (en) * 1999-05-13 2003-09-02 Tadiran Telecom Business Systems Ltd. Method and apparatus for downloading software into an embedded-system
US6658461B1 (en) * 2000-05-25 2003-12-02 International Business Machines Corporation Method of, system for, and computer program product for providing a user interface for configuring connections between a local workstation file system and a remote host file system
US6691125B1 (en) * 1999-11-17 2004-02-10 Serena Software, Inc. Method and apparatus for converting files stored on a mainframe computer for use by a client computer
US6718372B1 (en) * 2000-01-07 2004-04-06 Emc Corporation Methods and apparatus for providing access by a first computing system to data stored in a shared storage device managed by a second computing system
US6757699B2 (en) * 2000-10-06 2004-06-29 Franciscan University Of Steubenville Method and system for fragmenting and reconstituting data
US6782400B2 (en) * 2001-06-21 2004-08-24 International Business Machines Corporation Method and system for transferring data between server systems
US6842793B2 (en) * 2002-03-28 2005-01-11 Hitachi, Ltd. Method and apparatus for verifying data in a storage system
US6850962B1 (en) * 1999-05-07 2005-02-01 Commercequest, Inc. File transfer system and method
US6850987B1 (en) * 1999-06-01 2005-02-01 Fastforward Networks, Inc. System for multipoint infrastructure transport in a computer network
US6854006B1 (en) * 1999-05-31 2005-02-08 International Business Machines Corporation System and method for merging web based on-demand SNA application selection and TN3270 client launching
US6854112B2 (en) * 2001-08-29 2005-02-08 International Business Machines Corporation System and method for the automatic installation and configuration of an operating system
US6857074B2 (en) * 1995-04-28 2005-02-15 J2 Global Communication, Inc. Systems and methods for storing, delivering, and managing messages
US6859899B2 (en) * 2000-05-15 2005-02-22 Texas Instruments Incorporated Method for data packet acquisition using split preamble
US6865737B1 (en) * 2000-08-23 2005-03-08 Microsoft Corporation Remote software installation and maintenance
US6868487B2 (en) * 2001-10-01 2005-03-15 International Business Machines Corporation Data storage device and method for storing information using alternate information storage architectures
US6871271B2 (en) * 2000-12-21 2005-03-22 Emc Corporation Incrementally restoring a mass storage device to a prior state
US6873991B2 (en) * 2002-10-02 2005-03-29 Matter Associates, L.P. System and method for organizing information
US6879988B2 (en) * 2000-03-09 2005-04-12 Pkware System and method for manipulating and managing computer archive files
US6889376B1 (en) * 1999-05-12 2005-05-03 Treetop Ventures, Llc Method for migrating from one computer to another
US6912629B1 (en) * 1999-07-28 2005-06-28 Storage Technology Corporation System and method for restoring data from secondary volume to primary volume in a data storage system
US6996576B2 (en) * 2000-11-22 2006-02-07 Bmc Software, Inc. Database management system and method which automatically schedules and performs actions and monitors results
US7028093B2 (en) * 2000-08-05 2006-04-11 Alcatel Method of transferring user data packets
US7133894B2 (en) * 2002-03-12 2006-11-07 International Business Machines Corporation Method, apparatus, and program for synchronous remote builds
US7171606B2 (en) * 2003-03-25 2007-01-30 Wegener Communications, Inc. Software download control system, apparatus and method
US7191197B2 (en) * 2002-05-22 2007-03-13 Hitachi, Ltd. Method and apparatus for detecting and transferring data of different formats
US20090157758A1 (en) * 2000-11-29 2009-06-18 Hyung Sup Lee Distribution of mainframe data in the PC environment

Family Cites Families (38)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3820079A (en) * 1971-11-01 1974-06-25 Hewlett Packard Co Bus oriented,modular,multiprocessing computer
US5369778A (en) * 1987-08-21 1994-11-29 Wang Laboratories, Inc. Data processor that customizes program behavior by using a resource retrieval capability
US5261080A (en) * 1987-08-21 1993-11-09 Wang Laboratories, Inc. Matchmaker for assisting and executing the providing and conversion of data between objects in a data processing system storing data in typed objects having different data formats
US5226161A (en) * 1987-08-21 1993-07-06 Wang Laboratories, Inc. Integration of data between typed data structures by mutual direct invocation between data managers corresponding to data types
US5109515A (en) * 1987-09-28 1992-04-28 At&T Bell Laboratories User and application program transparent resource sharing multiple computer interface architecture with kernel process level transfer of user requested services
US5455926A (en) * 1988-04-05 1995-10-03 Data/Ware Development, Inc. Virtual addressing of optical storage media as magnetic tape equivalents
US4999766A (en) * 1988-06-13 1991-03-12 International Business Machines Corporation Managing host to workstation file transfer
US4939670A (en) * 1988-11-18 1990-07-03 Unisys Corporation PC driven print file utilities for mainframe computer printing
US5016277A (en) * 1988-12-09 1991-05-14 The Exchange System Limited Partnership Encryption key entry method in a microcomputer-based encryption system
US5128996A (en) * 1988-12-09 1992-07-07 The Exchange System Limited Partnership Multichannel data encryption device
US5175766A (en) * 1988-12-09 1992-12-29 The Exchange System Limited Partnership Signalling scheme for controlling data encryption device in an electronic fund transaction processing system
US5439509A (en) * 1991-01-22 1995-08-08 Turbotak Inc. Stripping method and apparatus
US5307262A (en) * 1992-01-29 1994-04-26 Applied Medical Data, Inc. Patient data quality review method and system
US5390314A (en) * 1992-10-09 1995-02-14 American Airlines, Inc. Method and apparatus for developing scripts that access mainframe resources that can be executed on various computer systems having different interface languages without modification
US5329619A (en) * 1992-10-30 1994-07-12 Software Ag Cooperative processing interface and communication broker for heterogeneous computing environments
US5611066A (en) * 1994-02-28 1997-03-11 Data/Ware Development, Inc. System for creating related sets via once caching common file with each unique control file associated within the set to create a unique record image
US5559933A (en) * 1994-04-22 1996-09-24 Unisys Corporation Distributed enterprise print controller
US5745748A (en) * 1994-12-09 1998-04-28 Sprint Communication Co. L.P. System and method for direct accessing of remote data
US5678044A (en) * 1995-06-02 1997-10-14 Electronic Data Systems Corporation System and method for improved rehosting of software systems
US5813009A (en) * 1995-07-28 1998-09-22 Univirtual Corp. Computer based records management system method
US5933623A (en) * 1995-10-26 1999-08-03 Hitachi, Ltd. Synchronous data transfer system
US5742818A (en) * 1995-12-15 1998-04-21 Microsoft Corporation Method and system of converting data from a source file system to a target file system
US6405294B1 (en) * 1995-12-29 2002-06-11 Mci Communications Corporation Data center migration method and system using data mirroring
US5987251A (en) * 1997-09-03 1999-11-16 Mci Communications Corporation Automated document checking tool for checking sufficiency of documentation of program instructions
US7225249B1 (en) * 1997-09-26 2007-05-29 Mci, Llc Integrated systems for providing communications network management services and interactive generating invoice documents
AU757557B2 (en) * 1997-11-13 2003-02-27 Intellectual Ventures I Llc File transfer system
AU2097099A (en) * 1997-12-31 1999-07-19 Kenneth J. Todd Dynamically configurable electronic comment card
US6178430B1 (en) * 1998-05-11 2001-01-23 Mci Communication Corporation Automated information technology standards management system
US6321276B1 (en) * 1998-08-04 2001-11-20 Microsoft Corporation Recoverable methods and systems for processing input/output requests including virtual memory addresses
US6594701B1 (en) * 1998-08-04 2003-07-15 Microsoft Corporation Credit-based methods and systems for controlling data flow between a sender and a receiver with reduced copying of data
US6233252B1 (en) * 1999-02-16 2001-05-15 Cyberstar, L.P. Transfer of very large digital data files via a fragmentation and reassembly methodology
WO2000070531A2 (en) * 1999-05-17 2000-11-23 The Foxboro Company Methods and apparatus for control configuration
US7272815B1 (en) * 1999-05-17 2007-09-18 Invensys Systems, Inc. Methods and apparatus for control configuration with versioning, security, composite blocks, edit selection, object swapping, formulaic values and other aspects
US7020697B1 (en) * 1999-10-01 2006-03-28 Accenture Llp Architectures for netcentric computing systems
US6609246B1 (en) * 1999-12-07 2003-08-19 Bull Hn Information Systems Inc. Integrated development environment for high speed transaction processing WWW applications on heterogeneous computer systems
US7685313B1 (en) * 2000-05-31 2010-03-23 International Business Machines Corporation Universal conversion server
JP4265087B2 (en) * 2000-06-29 2009-05-20 ソニー株式会社 Data conversion apparatus and method, data transmission / reception apparatus and method, and network system
US20030110265A1 (en) * 2001-12-07 2003-06-12 Inrange Technologies Inc. Method and apparatus for providing a virtual shared device

Patent Citations (53)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4807224A (en) * 1987-08-21 1989-02-21 Naron Steven E Multicast data distribution system and method
US4855900A (en) * 1987-10-28 1989-08-08 Recognition Equipment Incorporated System for transferring data to a mainframe computer
US4893307A (en) * 1988-02-29 1990-01-09 International Business Machines Corporation Method and apparatus for linking SNA terminals to an SNA host over a packet switched communications network
US6115710A (en) * 1989-09-28 2000-09-05 Sterling Software, Inc. Portable and dynamic distributed transaction management method
US5438509A (en) * 1991-02-07 1995-08-01 Heffron; Donald J. Transaction processing in a distributed data processing system
US5812864A (en) * 1991-07-09 1998-09-22 International Business Machines Corporation Personal computer/host emulation system for handling host data with personal computer application programs at personal computers
US5530848A (en) * 1992-10-15 1996-06-25 The Dow Chemical Company System and method for implementing an interface between an external process and transaction processing system
US6857074B2 (en) * 1995-04-28 2005-02-15 J2 Global Communication, Inc. Systems and methods for storing, delivering, and managing messages
US5732275A (en) * 1996-01-11 1998-03-24 Apple Computer, Inc. Method and apparatus for managing and automatically updating software programs
US6205579B1 (en) * 1996-10-28 2001-03-20 Altera Corporation Method for providing remote software technical support
US5937197A (en) * 1996-11-06 1999-08-10 Ncr Corporation Updating of electronic performance support systems by remote parties
US5999740A (en) * 1996-11-08 1999-12-07 International Computers Limited Updating mechanism for software
US6529976B1 (en) * 1997-04-01 2003-03-04 Hitachi, Ltd. Heterogeneous computer system, heterogeneous input output system and data back-up method for the systems
US6385654B1 (en) * 1997-10-23 2002-05-07 International Business Machines Corporation File transferring apparatus and method thereof
US6074435A (en) * 1997-10-30 2000-06-13 Telefonakiebolaget Lm Ericsson (Publ) Remote software download with automatic adjustment for data access compatibility
US6023710A (en) * 1997-12-23 2000-02-08 Microsoft Corporation System and method for long-term administration of archival storage
US6532463B1 (en) * 1998-12-01 2003-03-11 University Of Florida Web page accessing of data bases and mainframes
US6536039B2 (en) * 1998-12-24 2003-03-18 Avaya Technology Corp. Software for seamless interconnectivity between active program modules on integrated arrangement of CD drive, data server, and PC hard disk drive
US6502106B1 (en) * 1999-03-25 2002-12-31 International Business Machines Corporation System, method, and program for accessing secondary storage in a network system
US6850962B1 (en) * 1999-05-07 2005-02-01 Commercequest, Inc. File transfer system and method
US6889376B1 (en) * 1999-05-12 2005-05-03 Treetop Ventures, Llc Method for migrating from one computer to another
US6615404B1 (en) * 1999-05-13 2003-09-02 Tadiran Telecom Business Systems Ltd. Method and apparatus for downloading software into an embedded-system
US6854006B1 (en) * 1999-05-31 2005-02-08 International Business Machines Corporation System and method for merging web based on-demand SNA application selection and TN3270 client launching
US6850987B1 (en) * 1999-06-01 2005-02-01 Fastforward Networks, Inc. System for multipoint infrastructure transport in a computer network
US6912629B1 (en) * 1999-07-28 2005-06-28 Storage Technology Corporation System and method for restoring data from secondary volume to primary volume in a data storage system
US6546474B1 (en) * 1999-08-07 2003-04-08 International Business Machines Corporation Method and system for the fast backup and transmission of data
US6571282B1 (en) * 1999-08-31 2003-05-27 Accenture Llp Block-based communication in a communication services patterns environment
US6332163B1 (en) * 1999-09-01 2001-12-18 Accenture, Llp Method for providing communication services over a computer network system
US6493871B1 (en) * 1999-09-16 2002-12-10 Microsoft Corporation Method and system for downloading updates for software installation
US6513048B1 (en) * 1999-11-17 2003-01-28 Serena Software, Inc. Method and apparatus for access to files stored on a mainframe using a personal computer user interface
US6691125B1 (en) * 1999-11-17 2004-02-10 Serena Software, Inc. Method and apparatus for converting files stored on a mainframe computer for use by a client computer
US6480834B1 (en) * 1999-11-17 2002-11-12 Serena Software, Inc. Method and apparatus for serving files from a mainframe to one or more clients
US6718372B1 (en) * 2000-01-07 2004-04-06 Emc Corporation Methods and apparatus for providing access by a first computing system to data stored in a shared storage device managed by a second computing system
US6879988B2 (en) * 2000-03-09 2005-04-12 Pkware System and method for manipulating and managing computer archive files
US6601212B1 (en) * 2000-03-29 2003-07-29 Hewlett-Packard Development Company, Lp. Method and apparatus for downloading firmware to a non-volatile memory
US6859899B2 (en) * 2000-05-15 2005-02-22 Texas Instruments Incorporated Method for data packet acquisition using split preamble
US6658461B1 (en) * 2000-05-25 2003-12-02 International Business Machines Corporation Method of, system for, and computer program product for providing a user interface for configuring connections between a local workstation file system and a remote host file system
US7028093B2 (en) * 2000-08-05 2006-04-11 Alcatel Method of transferring user data packets
US6457109B1 (en) * 2000-08-18 2002-09-24 Storage Technology Corporation Method and apparatus for copying data from one storage system to another storage system
US6865737B1 (en) * 2000-08-23 2005-03-08 Microsoft Corporation Remote software installation and maintenance
US6757699B2 (en) * 2000-10-06 2004-06-29 Franciscan University Of Steubenville Method and system for fragmenting and reconstituting data
US6996576B2 (en) * 2000-11-22 2006-02-07 Bmc Software, Inc. Database management system and method which automatically schedules and performs actions and monitors results
US20090157758A1 (en) * 2000-11-29 2009-06-18 Hyung Sup Lee Distribution of mainframe data in the PC environment
US8868515B2 (en) * 2000-11-29 2014-10-21 Hyung Sup Lee Distribution of mainframe data in the PC environment
US6871271B2 (en) * 2000-12-21 2005-03-22 Emc Corporation Incrementally restoring a mass storage device to a prior state
US6782400B2 (en) * 2001-06-21 2004-08-24 International Business Machines Corporation Method and system for transferring data between server systems
US6854112B2 (en) * 2001-08-29 2005-02-08 International Business Machines Corporation System and method for the automatic installation and configuration of an operating system
US6868487B2 (en) * 2001-10-01 2005-03-15 International Business Machines Corporation Data storage device and method for storing information using alternate information storage architectures
US7133894B2 (en) * 2002-03-12 2006-11-07 International Business Machines Corporation Method, apparatus, and program for synchronous remote builds
US6842793B2 (en) * 2002-03-28 2005-01-11 Hitachi, Ltd. Method and apparatus for verifying data in a storage system
US7191197B2 (en) * 2002-05-22 2007-03-13 Hitachi, Ltd. Method and apparatus for detecting and transferring data of different formats
US6873991B2 (en) * 2002-10-02 2005-03-29 Matter Associates, L.P. System and method for organizing information
US7171606B2 (en) * 2003-03-25 2007-01-30 Wegener Communications, Inc. Software download control system, apparatus and method

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"COMM-PRESS(TM) Version 4.4, User's Guide" , April 1999, Comm-Press Technologies, Inc., 124 pages. *
eHow, "How to Modify the Creation Date of a Word Document", retrieved on 9/3/2012, from eHow.com, 3 pages. *
Micro Focus, "Micro Focus Mainframe Express(TM) - Administrator's Guide", June 1999, Issue 2, MERANT International Limited, downloaded from http://support.microfocus.com/documentation/books/mx20books/ugpubb02.htm, Chapters 1-5, 46 pages. *
Micro Focus, "Micro Focus Mainframe Express(TM) - User's Guide", June 1999, Issue 2, MERANT International Limited, downloaded from http://support.microfocus.com/documentation/books/mx20books/ugpubb02.htm, Chapters 1, 10-13, 34 pages. *

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090157758A1 (en) * 2000-11-29 2009-06-18 Hyung Sup Lee Distribution of mainframe data in the PC environment
US8868515B2 (en) * 2000-11-29 2014-10-21 Hyung Sup Lee Distribution of mainframe data in the PC environment
US20080275944A1 (en) * 2007-05-04 2008-11-06 International Business Machines Corporation Transaction-initiated batch processing
US7958188B2 (en) * 2007-05-04 2011-06-07 International Business Machines Corporation Transaction-initiated batch processing
US20110197194A1 (en) * 2007-05-04 2011-08-11 International Business Machines Corporation Transaction-initiated batch processing
US8495136B2 (en) 2007-05-04 2013-07-23 International Business Machines Corporation Transaction-initiated batch processing
US7689905B1 (en) * 2008-11-05 2010-03-30 International Business Machines Corporation Containment of terminal application run-time data for viewing when disconnected from a host server
US10754733B2 (en) 2015-07-16 2020-08-25 Gil Peleg System and method for mainframe computers backup and restore
CN105610957A (en) * 2016-01-07 2016-05-25 中国联合网络通信集团有限公司 Cloud system and data synchronization method thereof
US11061605B1 (en) 2020-01-09 2021-07-13 International Business Machines Corporation Dynamically performing managed file transfer based on policies

Also Published As

Publication number Publication date
US8868515B2 (en) 2014-10-21
US6886160B1 (en) 2005-04-26
US20090157758A1 (en) 2009-06-18

Similar Documents

Publication Publication Date Title
US20050038830A1 (en) Distribution of mainframe data in the PC environment
US7634491B2 (en) Method and system for relocating files that are partially stored in remote storage
US7668901B2 (en) Methods and system using a local proxy server to process media data for local area users
US20020099726A1 (en) Method and system for distribution of file updates
US5832274A (en) Method and system for migrating files from a first environment to a second environment
US6189051B1 (en) System and method for manufacturing hard disk master by downloading selected programs and drivers from a host through a network
US6973647B2 (en) Preferable modes of software package deployment
US6928644B1 (en) Method for configuring software for a build to order system
US7356816B2 (en) Method and apparatus for multiplatform migration
US7293272B1 (en) Device driver processing for automated system restores
KR100868410B1 (en) Managed file system filter model and architecture
US7603405B2 (en) Information processing system, information processing method, and storage medium therefor
US6223345B1 (en) System and method for building client and server application packages
JP4095971B2 (en) Using virtual targets to create and process requests for server-free data transfer operations
US20030131285A1 (en) Automated system that tests software on multiple computers
US20060047716A1 (en) Transaction based virtual file system optimized for high-latency network connections
US20030221094A1 (en) Method and system for configuring a computer
US20040098426A1 (en) Backup system, backup method, program for backup, and backup service provision system
US20080282180A1 (en) Data Transfer Using A Network Clipboard
US6847987B2 (en) System and method for extending client-server software to additional client platforms for servicing thin clients requests
TW200305319A (en) Delta replication of source files and packages across networked resources
US20080002694A1 (en) Method to accelerate NDMP based virtual tape library operations
US7752169B2 (en) Method, system and program product for centrally managing computer backups
JPH05241923A (en) File converting device
US20030236927A1 (en) Tool for building multiple OS images

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION