Data management system, apparatus, and method to use buffered file marks
Summary by NHIP
Buffered tape mark recording
The method records information on a data storage medium by transferring data from memory buffers after configuring a Dataset Control Block. This process sets a buffered tape mark indicator and issues a SYNC=NONE command while enabling a DCBESYN_NONE attribute and a UCBCX_BUFFTM attribute.
Claim Score by NHIP
Abstract
A method to record information on a data storage medium using buffered tape marks. A data storage device comprising a computer useable medium having computer readable program code disposed therein for implementing Applicants' method to record information on a data storage medium using buffered tape marks. A data storage and retrieval system comprising a computer useable medium having computer readable program code disposed therein for implementing Applicants' method to record information on a data storage medium using buffered tape marks. Computer program products embodied as program code stored in one or more memory devices, such as a magnetic disk, a magnetic tape, or other non-volatile memory device disposed in a host computer, a data storage device, and/or a library controller.

Term
Term ended
Expired 10 January 2022, 4.7 years ago.
- Priority and filed
- Granted
- Expired
- Today
9 claims: 3 independent, 6 dependent
- 1Broadest claimClaim Score 45, average(NHIP)A method to record information on a data storage medium using buffered tape marks, comprising the steps of:providing a data storage and retrieval system comprising a host computer, one or more memory buffers, an operating system, and a data storage device;configuring said data storage and retrieval system to allow use of buffered tape marks;providing information from said host, wherein said information includes one or more tape marks;providing a Dataset Control Block along with said information;setting a buffered tape mark indicator in said Dataset Control Block to request use of buffered tape marks;storing said information in said one or more memory buffers;removeably disposing said data storage medium in said data storage device;and transferring said information from said one or more memory buffers to said data storage medium.
- 4A data storage and retrieval system comprising a computer useable medium having computer readable program code disposed therein for recording information using buffered tape marks, wherein said data storage and retrieval system comprises a host computer, one or more memory buffers, an operating system, a data storage device, and a data storage medium removeably disposed in said data storage device, the computer readable program code comprising a series of computer readable program steps to effect:configuring said data storage and retrieval system to allow use of buffered tape marks;providing information from said host computer, wherein said information comprises one or more tape marks;providing a Dataset Control Block along with said information;setting a buffered tape mark indicator in said Dataset Control Block to request use of buffered tape marks;storing said information in said one or more memory buffers: and transferring said information from said one or more memory buffers to said data storage medium.
- 8A computer program product usable with a programmable computer processor having computer readable program code embodied therein for recording information using buffered tape marks, comprising:a DCBESYN_NONE attribute;a SYNC=NONE command;computer readable program code which causes said programmable computer processor to issue said SYNC=NONE command;and computer readable program code which causes said programmable computer processor to set said DCBESYN_NONE attribute to ON;computer readable program code which causes said programmable computer processor to configure said data storage and retrieval system to allow use of buffered tape marks;computer readable program code which causes said programmable computer processor to provide information, wherein said information comprises one or more tape marks;computer readable program code which causes said programmable computer processor to store said information in a memory buffer;and computer readable program code which causes said programmable computer processor to transfer said information from said memory buffer to a data storage medium.
Independent claims3
66 paragraphs in 5 sections, as filed
FIELD OF THE INVENTION
Applicant's invention relates to an apparatus and method to record information on a data storage medium using buffered file marks.
BACKGROUND OF THE INVENTION
Automated media storage libraries are known for providing cost effective access to large quantities of stored media. Generally, media storage libraries include a large number of storage slots in which are stored data storage media. The portable data storage media are typically housed in a portable container, such as a tape cartridge, an optical cartridge, and the like. One (or more) accessors typically access the data storage media from the storage slots and deliver the accessed media to a data storage drive for reading and/or writing data on the accessed media. Suitable electronics operate the accessor(s) and operate the data storage drive(s) to transmit to, and/or to receive data from, an attached on-line host computer system.
In a conventional automated media storage library, the storage slots are arranged in a planar orthogonal arrangement forming a “wall” of storage slots for holding data storage media. The plane may be a flat plane, or may be a cylindrical plane. To double the storage capacity, two “walls” of storage slots may be provided on either side of the accessor.
A number of different companies manufacture automated media storage libraries today, each model displaying various different features. One example is the IBM 3494 Media Storage Library. Some of the automated media storage libraries have dual or multiple accessors to provide a level of redundancy and/or improved performance.
What is needed, however, is a data management system, method, and apparatus and method to expedite the recording of information provided by a host computer onto a data storage medium, particularly where that information comprises a plurality of individual files.
SUMMARY OF THE INVENTION
Applicants' invention includes a method to dispose information on a sequential medium, such as a tape, using buffered tape marks. Applicants' method includes the steps of providing information from a host computer to a tape library, where that information includes one or more tape marks, storing that information in one or more memory buffers, and transferring that information from those one or more memory buffers to a data storage medium.
Applicants' invention further includes a data storage device which includes a computer useable medium having computer readable program code disposed therein for disposing information on a data storage medium using buffered tape marks. Applicants' invention further includes a data storage and retrieval system comprising a computer useable medium having computer readable program code disposed therein for disposing information on a data storage medium using buffered tape marks.
Applicants' invention further includes a computer program product usable with a programmable computer processor having computer readable program code embodied therein for disposing information on a tape medium using buffered tape marks.
BRIEF DESCRIPTION OF THE DRAWINGS
The invention will be better understood from a reading of the following detailed description taken in conjunction with the drawings in which like reference designators are used to designate like elements, and in which:
FIG. 1 is a perspective view of a first embodiment of Applicants' data storage and retrieval system;
FIG. 2A is a block diagram of a controller disposed in Applicants' data storage device;
FIG. 2B is a block diagram of a controller disposed in Applicants' data storage and retrieval system;
FIG. 3 is block diagram showing the components of Applicants' data storage and retrieval system;
FIG. 4 is a perspective view of a second embodiment of Applicants' data storage and retrieval system;
FIG. 5 is a block diagram showing the disposition of information disposed on a data storage tape medium;
FIG. 6A is a block diagram showing certain steps of a prior art method to write information to a data storage tape medium;
FIG. 6B is a block diagram showing certain steps of a prior art method to write information to a data storage tape medium;
FIG. 6C is a block diagram showing certain steps of a prior art method to write information to a data storage tape medium;
FIG. 6D is a block diagram showing certain steps of a prior art method to write information to a data storage tape medium;
FIG. 6E is a block diagram showing certain steps of a prior art method to write information to a data storage tape medium;
FIG. 7 is a flowchart summarizing Applicants' method to use buffered tape marks;
FIG. 8 is a flowchart summarizing the initial steps in Applicants' method to write information to a data storage tape medium;
FIG. 9 is a flowchart summarizing the steps of prior art methods to write information to a data storage tape medium.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
Referring to the illustrations, like numerals correspond to like parts depicted in the figures. The invention will be described as embodied in an automated data storage and retrieval subsystem for use in a data processing environment. The following description of Applicant's method to record information to a movable tape medium, or to a movable tape medium disposed within a portable data storage cartridge is not meant, however, to limit Applicant's invention to either data storage and retrieval systems, or to magnetic tape applications, as the invention herein can be applied to data storage media in general.
FIG. 3 illustrates the hardware and software environment in which preferred embodiments of the present invention are implemented. Host system <b>390</b> includes Applicants' hierarchical storage management (HSM) program <b>310</b>. Host computer <b>390</b> can comprises one or more mainframe computers, one or more personal computers, and combinations thereof.
Information is transferred between the host system <b>390</b> and secondary storage devices managed by a data storage and retrieval system, such as tape subsystem <b>320</b>, via communication link <b>350</b>. Communication link <b>350</b> comprises a serial interconnection, such as an RS-232 cable or an RS-432 cable, an ethernet interconnection, a SCSI interconnection, a Fiber Channel interconnection, an ESCON network, a FICON network, a Local Area Network (LAN), a private Wide Area Network (WAN), a public wide area network, Storage Area Network (SAN), Transmission Control Protocol/Internet Protocol (TCP/IP), the Internet, and combinations thereof.
In the embodiment shown in FIG. 3, tape subsystem <b>320</b> includes tape drives <b>330</b> and <b>340</b>. In other embodiments of Applicants' data storage and retrieval system, tape subsystem <b>320</b> includes a single data storage drive. In alternative embodiments, Applicants' data storage and retrieval system <b>320</b> includes more than two data storage drives.
A plurality of portable data storage media <b>360</b> are stored within Applicants' data storage and retrieval system. In certain embodiments, plurality of data storage media <b>360</b> are each housed in a portable data storage cartridge <b>370</b>, such as plurality of portable tape cartridges <b>370</b> (not shown in FIG. <b>3</b>). Each of such portable data storage cartridges may be inserted in one of tape drives, and thereafter accessed by the tape subsystem <b>320</b>. In alternative embodiments, alternative storage media may be substituted for the tape cartridges <b>370</b>. Any type of non-volatile sequential media supporting a sequential access command architecture could be used.
The tape subsystem <b>320</b> further includes program logic to manage tape drives <b>330</b> and <b>340</b>, and plurality of tape cartridges <b>370</b>. In alternative embodiments, tape subsystem <b>330</b> and host system <b>390</b> may be located on a single computer machine.
Host system <b>390</b> comprises a computer system, such as a mainframe, personal computer, workstation, etc., including an operating system such as Windows, AIX, Unix, MVS, etc. (Windows is a registered trademark of Microsoft Corporation; AIX is a registered trademark and MVS is a trademark of IBM Corporation; and UNIX is a registered trademark in the United States and other countries licensed exclusively through The Open Group.) The HSM program <b>310</b> in the host system <b>390</b> may include the functionality of HSM type programs known in the art that manage the transfer of data to a tape library, such as the IBM DFSMS implemented in the IBM MVS operating system.
The IBM DFSMS software is described in “DFSMS/MVS V1R4 General Information,” IBM document no. GC26-4900-05, published by IBM (Copyright 1997, IBM), which publication is incorporated herein by reference in its entirety. In addition to including known HSM functions, such as recall and migration, the HSM program <b>310</b> would further include additional program instructions to perform the operations of the preferred embodiments of the present invention. The HSM program <b>310</b> may be implemented within the operating system of the host system <b>390</b> or as a separate, installed application program.
The tape subsystem <b>320</b> comprises a computer system, and manages a plurality of tape drives and tape cartridges. The tape drives <b>330</b> and <b>340</b> may be any suitable tape drives known in the art, e.g., the Magstar 3590 tape drives. Tape cartridges <b>370</b> may be any suitable tape cartridge device known in the art, (Magstar is a registered trademark of IBM Corporation) such as ECCST, Magstar, IBM 3420, 3480, 3490E, 3590 tape cartridges, etc. The tape subsystem <b>320</b> may be a manual tape library in which the user must manually mount tape cartridges <b>370</b> into the tape drives <b>330</b>/<b>340</b>, or an automated tape library (ATL) in which a robotic arm mounts tape cartridges <b>370</b> in the library into the tape drives <b>330</b>/<b>340</b>.
For example referring now to FIG. 1, automated data storage and retrieval system <b>100</b> is shown having a first wall of storage slots <b>102</b> and a second wall of storage slots <b>104</b>. Portable data storage cartridges, such as tape cartridges <b>370</b>, are individually stored in these storage slots.
Data storage and retrieval system <b>100</b> includes one or more accessors, such as accessors <b>110</b> and <b>120</b>. An accessor is a robotic device which accesses portable data storage media from first storage wall <b>102</b> or second storage wall <b>104</b>, delivers that accessed media to data storage devices <b>130</b>/<b>140</b> for reading and/or writing data thereon, and returns the media to the proper storage slot.
Referring now to FIG. 2A, data storage device <b>130</b> includes device controller <b>232</b>. Controller <b>232</b> includes microprocessor <b>234</b> in communication with memory <b>236</b>. In certain embodiments, microprocessor <b>234</b> communicates with memory <b>236</b> via communication link <b>235</b>. In other embodiments, memory <b>236</b> is integral to microprocessor <b>234</b>. Device microcode <b>238</b> is stored in memory <b>236</b>. Device microcode comprises a computer program product which controls the operation of a data storage device, such as data storage device <b>130</b> (FIG. <b>1</b>)/<b>140</b> (FIG. <b>1</b>)/<b>430</b> (FIG. <b>4</b>).
Referring again to FIG. 1, in certain embodiments, library controller <b>160</b> is integral with host <b>390</b>. In other embodiments, controller <b>160</b> is external to host <b>390</b>. In those external embodiments, library controller <b>160</b> (FIG. 1) communicates with host computer <b>390</b> (FIGS. 1, <b>3</b>) via communication link <b>392</b>.
Referring now to FIG. 2B, library controller <b>160</b> includes microprocessor <b>262</b>, volatile memory <b>264</b>, and non-volatile memory <b>266</b>. In certain embodiments, microprocessor communicates with volatile memory <b>264</b> via communication link <b>263</b>. In other embodiments, volatile memory <b>264</b> is integral to microprocessor <b>262</b>. Microprocessor <b>262</b> communicates with non-volatile memory <b>266</b> via communication link <b>265</b>. Library operating system <b>268</b> is stored in non-volatile memory <b>266</b>. Operating system <b>268</b> comprises a computer program product which controls the operation of data storage and retrieval systems <b>100</b> (FIG. <b>1</b>)/<b>400</b> (FIG. <b>4</b>), and tape subsystem <b>320</b> (FIG. <b>3</b>).
Referring again to FIG. 1, operator input station <b>150</b> permits a user to communicate with Applicant's automated data storage and retrieval system <b>100</b>. Devices <b>180</b> and <b>190</b> each comprise information buffers. In certain embodiments, devices <b>180</b> and/or <b>190</b> comprise a Direct Access Storage Device (“DASD”) cache. In certain embodiments DASD cache <b>180</b> and <b>190</b> comprise a plurality of hard disk drives which are configured into one or more RAID arrays. In certain embodiments, information transferred between host computer <b>390</b> and data storage and retrieval system <b>100</b> is buffered in DASD caches <b>180</b> and <b>190</b> before being recorded on other data storage media, such as one or more magnetic tapes. Import/export station <b>172</b> includes access door <b>174</b> pivotably attached to the side of system <b>100</b>. Portable data storage cartridges can be placed in the system, or in the alternative, removed from the system, via station <b>172</b>/access door <b>174</b>.
FIG. 4 shows system <b>400</b> which comprises another embodiment of Applicant's data storage and retrieval system. System <b>400</b> includes first storage wall <b>402</b> and second storage wall <b>404</b>. Storage walls <b>402</b> and <b>404</b> each include a plurality of storage elements in which can be stored a plurality of portable data storage cartridges. System <b>400</b> includes one or more data storage devices, such as device <b>430</b>. Device <b>430</b> comprises a floppy disk drive, an optical disk drive, a magnetic tape drive, and the like. System <b>400</b> further includes operator control panel <b>450</b> (not shown in FIG. <b>3</b>).
System <b>400</b> further includes library controller <b>460</b>. Library controller <b>460</b> controls the operation of assessor <b>410</b> and data storage device <b>430</b>. Controller <b>460</b> is configured similarly to controller <b>160</b> shown in FIG. <b>2</b>B. System <b>400</b> further includes one or a plurality of portable data storage cartridges, such as tape cartridges <b>370</b>. Each cartridge contains a data storage media internally disposed therein, such as data storage media <b>360</b> (FIG. <b>3</b>).
Referring again to FIG. 3, tape subsystem <b>320</b>, such as data storage and retrieval system <b>100</b>/<b>200</b>, receives commands from the HSM program <b>310</b> in the host system <b>390</b> and performs the operations requested by the HSM program <b>310</b>, such as migration and recall, to transfer data between the host system <b>390</b> and the components managed by the tape subsystem <b>320</b>. In preferred embodiments, the tape subsystem <b>320</b> can simultaneously process numerous input/output requests from the host system <b>390</b> and any other attached system directed toward the tape drives <b>330</b>/<b>340</b> and tape cartridges <b>370</b> managed by the tape subsystem <b>320</b>. Moreover, in certain embodiments HSM program <b>310</b> in the host system <b>390</b> is capable of multi-tasking, simultaneously executing numerous input/output operations, and simultaneously transmitting multiple I/O requests to the tape subsystem <b>320</b> to execute.
In further embodiments, a plurality of host systems <b>390</b> may communicate with the tape subsystem <b>320</b> and/or a host system <b>390</b> may communicate and transfer data to a plurality of tape subsystems <b>320</b>, each subsystem providing access to a library of tape cartridges.
FIG. 5 shows a block diagram depicting an industry-standard image of information stored on a data storage medium, such as a portion of magnetic tape <b>500</b>. The information written on tape <b>500</b> includes file <b>520</b> and file <b>530</b>. File <b>520</b> is the (N)th file stored on tape <b>500</b> and file <b>530</b> is the (N+1)th file stored on tape <b>500</b>. Files <b>1</b> through (N−1) are stored on portion <b>510</b> of tape <b>500</b>.
File <b>520</b> includes header label group <b>521</b>, data <b>523</b>, and trailer label group <b>525</b>. Tape mark <b>522</b> is disposed between header label group <b>521</b> and data <b>523</b>. Tape mark <b>524</b> is disposed between data <b>523</b> and trailer label group <b>525</b>. Tape mark <b>526</b> is disposed after trailer label group <b>525</b>. Thus, file <b>520</b> includes three (3) tape marks, i.e. tape marks <b>522</b>, <b>524</b>, and <b>526</b>.
File <b>530</b> includes header label group <b>531</b>, data <b>533</b>, and trailer label group <b>535</b>. Tape mark <b>532</b> is disposed between header label group <b>531</b> and data <b>533</b>. Tape mark <b>534</b> is disposed between data <b>533</b> and trailer label group <b>535</b>. Tape mark <b>536</b> is disposed after trailer label group <b>535</b>. Thus, file <b>530</b> includes three (3) tape marks, i.e. tape marks <b>532</b>, <b>534</b>, and <b>536</b>.
Tape mark <b>540</b> is disposed after tape mark <b>536</b>. Tape mark <b>536</b> in combination with tape mark <b>540</b> comprises double tape mark <b>550</b>. Double tape mark <b>550</b> signifies that file <b>530</b> is the last file written on tape <b>500</b>. Thus, portion <b>560</b> of tape <b>500</b> contains no information.
FIGS. 6A-6E, <b>8</b>, and <b>9</b>, illustrate prior art methods to write information to tape <b>600</b>. Referring to FIG. 6A, tape <b>600</b> includes (N−1) files. The (N−1)th file ends with trailer label group <b>620</b> followed by tape mark <b>630</b> and end of file tape mark <b>640</b>. Tape mark <b>630</b> in combination with tape mark <b>640</b> comprises double tape mark <b>650</b>. As noted above, double tape mark <b>650</b> identifies the end of information stored on tape <b>600</b>. Thus, no files are stored on portion <b>660</b> of tape <b>600</b>.
In step <b>810</b> (FIG. <b>8</b>), an attached host computer, such as host computer <b>390</b> (FIG. <b>3</b>), instructs a data storage device, such as data storage device <b>130</b> (FIG. <b>1</b>), to write new information on a designated data storage medium, such as tape <b>600</b>. In step <b>820</b> a robotic accessor, such as accessor <b>110</b> (FIG. <b>1</b>), retrieves and transports the portable data storage cartridge housing tape <b>600</b>. In step <b>830</b>, that portable data storage cartridge is inserted, i.e. mounted, in data storage device <b>130</b>.
In step <b>840</b>, data storage device <b>130</b> advances tape <b>600</b> in either the forward or the reverse direction as needed until double tape mark <b>650</b> is found. As those skilled in the art will appreciate, data storage device <b>130</b> includes read/write head <b>132</b> (not shown in FIGs.) internally disposed therein. Upon locating double tape mark <b>650</b>, the movement of tape <b>600</b> is stopped. In step <b>850</b>, a Back Space File command (“BSF”) command is issued to tape drive <b>130</b> and tape <b>600</b> is moved to position read/write head <b>132</b> between tape mark <b>630</b> and tape mark <b>640</b>, i.e. to about position <b>601</b> which is shown on FIG. <b>6</b>B. Read/write head <b>132</b> is positioned at about point <b>601</b> on tape <b>600</b> at time T<sub>0</sub>.
FIG. 9 summarizes the prior art method to write file <b>680</b> to tape <b>600</b> starting at about point <b>601</b>. Referring now to FIGS. 6C and 9, in step <b>910</b> header label group <b>681</b> is written to tape <b>600</b> starting at about position <b>601</b>. After header label group <b>681</b> is written to tape <b>600</b>, in step <b>920</b> tape mark <b>682</b> is written to tape <b>600</b> adjacent header label group <b>681</b>. After writing tape mark <b>682</b> to tape <b>600</b>, in step <b>930</b> data <b>683</b> is written to tape <b>600</b> adjacent tape mark <b>682</b>. In step <b>940</b> tape mark <b>684</b> is written to tape <b>600</b> adjacent data <b>683</b>. In step <b>950</b> trailer label group <b>685</b> is written to tape <b>600</b> adjacent tape mark <b>684</b>. In step <b>960</b> tape mark <b>686</b> is written to tape <b>600</b> adjacent trailer label group <b>685</b>. In step <b>970</b> tape mark <b>687</b> is written to tape <b>600</b> adjacent tape mark <b>686</b> to form double tape mark <b>690</b>.
After writing header label group <b>681</b>, tape mark <b>682</b>, data <b>683</b>, tape mark <b>684</b>, trailer label group <b>685</b> and tape mark <b>686</b>, at time T<sub>1 </sub>read/write head <b>132</b> is positioned at about point <b>602</b> of tape <b>600</b>. Those skilled in the art will appreciate that the time period between T<sub>0 </sub>and T<sub>1</sub>, ΔT<sub>Information Write</sub>, represents the time required to write file <b>680</b> to tape <b>600</b>. Thereafter, an end of file (“EOF”) tape mark <b>687</b> is written adjacent tape mark <b>687</b> to form double tape mark <b>690</b>. Referring now to FIG. 6D, at time T<sub>2 </sub>read/write head <b>132</b> is disposed adjacent point <b>603</b>.
In step <b>980</b> a Back Space File command is issued which causes tape <b>600</b> to move in the reverse direction such that read/write head <b>132</b> is positioned between tape marks <b>686</b> and <b>687</b>. Referring to FIG. 6E, in step <b>990</b> the tape is repositioned such that read/write head <b>132</b> is disposed at time T<sub>3 </sub>adjacent point <b>602</b> on tape <b>600</b>. Those skilled in the art will appreciate that the time interval between time T<sub>1 </sub>and time T<sub>3</sub>, i.e. ΔT<sub>Head Reposition</sub>, represents the time required to write a double tape mark and reposition tape <b>600</b> such read/write head <b>132</b> is disposed adjacent point <b>602</b>.
Using this prior art method, after writing each incremental file to tape <b>600</b> a double tape mark is first written, and then overwritten. The time to write/overwrite such a double tape mark includes three segments: (i) the time to synchronize buffered data to the data storage medium, (ii) the time to physically write the EOF tape mark, and (iii) the time to reposition the tape to dispose the read/write head between the two tape marks comprising the EOF double tape mark.
Applicants' method utilizing buffered tape marks eliminates temporal components (i), (ii), and (iii). Thus, when writing (N) files to a data storage medium, Applicants' method eliminates the need to synchronize buffered data to the medium (N) times, eliminates the need to write an EOF tape mark (N) times, and eliminates the need to reverse the direction of travel of the storage medium (N) times.
Applicants' invention comprises a data management system, apparatus, and method to write “buffered” tape marks to a data storage medium. As shown in FIG. 5, standard tape labeling protocols include writing a header label group, such as header label group <b>521</b>, a first tape mark, such as tape mark <b>522</b>, information, such as data <b>523</b>, a second tape mark, such as tape mark <b>524</b>, a trailer label group, such as trailer label group <b>525</b>, and a third tape mark, such as tape mark <b>526</b>. Thus, a typical “file” recorded on a data storage tape medium includes three tape marks disposed adjacent other file components.
As noted above, host computer <b>390</b> (FIG. 3) provides information to tape subsystem <b>320</b> (FIG. <b>3</b>), such as library <b>100</b>/<b>400</b>. In certain embodiments of Applicants' method, the information provided by host <b>390</b> is first stored in information buffers, such as DASD devices <b>180</b> (FIG. <b>1</b>)/<b>190</b> (FIG. <b>1</b>). The library controller, such as controller <b>160</b> (FIG. <b>1</b>)/<b>460</b> (FIG. 4) then transfers this information from the buffer to data storage media, such as tape <b>500</b> (FIG. <b>5</b>). In certain embodiments, the library operating system, such as operating system <b>268</b> (FIG. <b>2</b>B), and/or device microcode disposed in the data storage device, such as device microcode <b>238</b> (FIG. <b>2</b>A), interposes the requisite tape marks to the information provided by host computer <b>390</b>.
Certain applications running on host computer <b>390</b> (FIG. <b>3</b>), however, are capable of properly interposing tape marks between the other file components to create the requisite file image recorded on the data storage medium. Applicants' invention includes a data management system, apparatus, and method to utilize buffered tape marks. Using Applicants' invention, a host computer application capable of properly interposing tape marks and data provides both tape marks and information to the data library, such as library <b>100</b>/<b>400</b>. The data library operating system, such as operating system <b>268</b>, stores that information/multiple tape mark combination in the data library's buffers, such as DASD devices <b>180</b> (FIG. <b>1</b>)/<b>190</b> (FIG. <b>1</b>), before writing the information and tape marks to a data storage medium, such as tape <b>500</b>.
Applications running on host computer <b>390</b> which are capable of properly interposing tape marks and data include some sort of application programming interface (“API”) which describes the attributes of the data set, i.e. the file, to be recorded on a data storage medium. In certain embodiments of Applicants' method, this API comprises a Dataset Control Block (“DCB”). Such a DCB further comprises a Dataset Control Block Extension (“DCBE”) which includes parameters which can be manipulated independently of the application itself. Moreover, such a DCBE is dynamically changeable by the application at the dataset level.
In certain embodiments, the DCBE includes a DCBEFLG3 attribute, a DCBESYN_NONE attribute, a SYNC=NONE command, and a SYNC=SYSTEM command. The DCBEFLG3 attribute includes a 3 bit field comprising the DCBESYN_NONE attribute. In the event the host application invokes the SYNC=NONE command, then the operating system, such as operating system <b>168</b>, sets the DCBESYN_NONE attribute to “ON,” thereby enabling the use of buffered tape marks. In the event host application invokes the SYNC=SYSTEM command, then the operating system sets the DCBESYN_NONE attribute to “OFF,” thereby disallowing the use of buffered tape marks.
FIG. 7 summarizes Applicants' method to utilize buffered tape marks when recording information to a data storage medium. In step <b>710</b>, a user configures the data storage and retrieval system to allow use of buffered tape marks.
When a data storage device disposed in Applicants' data storage and retrieval system is allocated to write designated information on a designated data storage medium, in step <b>720</b> the operating system determines, among other things, if the host application providing the designated information has requested use of buffered tape marks. In the event the DCBESYN_NONE attribute is set to “ON,” then in step <b>1220</b> the library operating system sets a buffered tape mark indicator in that data storage device's unit control block extension (“UCB extension”). In certain embodiments, the buffered tape mark indicator comprises a UCBCX_BUFFTM attribute. If the operating system determines that use of buffered tape marks is enabled, then the operating system sets the UCBCX_BUFFTM indicator to “ON.”
In step <b>730</b> the host computer application checks the allocated data storage device's UCB extension to determine if buffered tape marks are enabled. In step <b>1240</b> the application requests the operating system use buffered tape marks when recording certain designated information to a designated data storage medium. In step <b>1250</b>, the operating system issues a MODE SET command to enable use of buffered tape marks. In certain embodiments, the data library operating system includes a MODE SET command. In these embodiments, the operating system issues a MODE SET command to persistently enable tape mark buffering for that designated information.
In step <b>760</b> the host computer application provides information which includes properly interposed tape marks to the data storage and retrieval system, such as data storage and retrieval system <b>100</b>/<b>400</b>. The information provided by the host computer comprises one or a plurality of data files, where each such data file includes, in the following order: a header label group, a first tape mark, data, a second tape mark, a trailer label group, and a third tape mark.
In step <b>770</b> the data storage and retrieval system stores that provided data files/tape mark combination in a memory buffer, such as DASD device <b>180</b> (FIG. <b>1</b>)/<b>190</b> (FIG. <b>1</b>). In step <b>780</b>, the data storage and retrieval system transfers the provided data files/tape mark combination to a designated data storage medium, such as tape <b>500</b> (FIG. 5) using a designated data storage device, such as device <b>130</b> (FIG. <b>1</b>)/<b>140</b> (FIG. <b>1</b>)/<b>430</b> (FIG. <b>4</b>).
Applicants' invention includes a data storage device comprising a computer useable medium having computer readable program code disposed therein for implementing Applicants' method to record information on a data storage medium. Applicants' invention further includes a data storage and retrieval system comprising a computer useable medium having computer readable program code disposed therein for implementing Applicants' method to record information on a data storage medium removeably disposed a data storage device disposed within Applicants' data storage and retrieval system. Applicants' invention further includes computer program products embodied as program code stored in one or more storage device, such as a magnetic disk, a magnetic tape, or other non-volatile memory device disposed, for example, in a host computer, a data storage device, or a library controller.
While the preferred embodiments of the present invention have been illustrated in detail, it should be apparent that modifications and adaptations to those embodiments may occur to one skilled in the art without departing from the scope of the present invention as set forth in the following claims.
Contents5
15 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15
Every citation, both waysCites: the store holds 0 of 1
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2003099056A1 | Cited by | United States of America | Pre-grant |
| WO2013073114A1 | Cited by | World Intellectual Property Organization (WIPO) | Applicant |
| US6909570B2 | Cited by | United States of America | Search report |
| US8862815B2 | Cited by | United States of America | Applicant |
| US6924954B2 | Cited by | United States of America | Search report |
| US9733839B2 | Cited by | United States of America | Search report |
| US2004100716A1 | Cited by | United States of America | Pre-grant |
| US2016004439A1 | Cited by | United States of America | Pre-grant |
| US8760781B2 | Cited by | United States of America | Applicant |
| US7463440B2 | Cited by | United States of America | Search report |
| US2005128624A1 | Cited by | United States of America | Pre-grant |
| IBM, DFSMS/MVS Version 1 Release 4, GC26-4900-05, General Information, 1980, pp. 1-167. | Non-patent | – | Applicant |
2 members in 1 office
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 96845201 | United States of America | A | |
| US20010968452 | – | – | – |
Members2
| Document | Office | Kind | |
|---|---|---|---|
| US2003065881A1 | United States of America | A1 | |
| US6711580B2This record | United States of America | B2 |
35 transactions on the USPTO file
Allowed after 1 non-final rejection.
- Non-final rejections
- 1
- Final rejections
- 0
- RCEs
- 0
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Expire PatentEXP. | EXP. | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Receipt into PubsR1021 | R1021 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Workflow - Drawings FinishedDRWF | DRWF | |
| Workflow - Drawings Matched with File at ContractorDRWM | DRWM | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Receipt into PubsR1021 | R1021 | |
| Receipt into PubsR1021 | R1021 | |
| Receipt into PubsR1021 | R1021 | |
| Workflow - File Sent to ContractorSENT | SENT | |
| Receipt into PubsR1021 | R1021 | |
| Dispatch to PublicationsD1220 | D1220 | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Correspondence Address ChangeC.AD | C.AD | |
| Information Disclosure Statement (IDS) Filed | – | |
| Information Disclosure Statement (IDS) Filed | – | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Application Is Now CompleteCOMP | COMP | |
| Additional Application Filing FeesADDFLFEE | ADDFLFEE | |
| A statement by one or more inventors satisfying the requirement under 35 USC 115, Oath of the ApplicOATHDECL | OATHDECL | |
| Notice Mailed--Application Incomplete--Filing Date AssignedINCD | INCD | |
| Correspondence Address ChangeC.AD | C.AD | |
| IFW Scan & PACR Auto Security Review | – | |
| Initial Exam Team nnIEXX | IEXX |
9 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Lapsed due to failure to pay maintenance feeLapsedFP | FP | |
| Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH | STCH | |
| Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH | STCH | |
| Lapse for failure to pay maintenance feesLapsedLAPS | LAPS | |
| Maintenance fee reminder mailedREMI | REMI | |
| Fee paymentFPAY | FPAY | |
| Fee paymentFPAY | FPAY | |
| Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| AssignmentAS | AS |
Numbers
- Publication, DOCDB
- 6711580
- Publication, EPODOC
- US6711580
- Application
- 9968452
- Application, DOCDB
- 96845201
- Application, EPODOC
- US20010968452
Titles
- English
- Data management system, apparatus, and method to use buffered file marks
Patent term adjustment
- A delay
- +226 daysthe office missed an examination deadline
- Applicant delay
- −125 days
- Net adjustment
- 101 days
Classification
- CPC, 9
- G11B27/107
- G06F3/0613
- G06F3/0656
- G06F3/0686
- G11B27/032
- G11B27/3027
- G11B2220/93
- Y10S707/99942
- Y10S707/99943
- IPC, 5
- G06F3 06
- G06F12 00
- G11B27 032
- G11B27 10
- G11B27 30
- USPC, 6
- 001001000
- 707999101
- 707999102
- G9B027011
- G9B027020
- G9B027033