# US 9,436,591 B1 · Out-of-band file transfers between a host and virtual tape server > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 9,436,591 B1 - Document ID: US9436591B1 - Status: Granted - Kind: B1 - Application number: 14/041,314 - Filed: 2013-09-30 - Granted: 2016-09-06 - Earliest claimed: 2013-09-30 - Assignees: EMC Corporation - Applicants: EMC Corporation - Inventors: Larry W. McCloskey; Karyn M. Kelley - Web page: https://patentgrep.com/patent/US9436591B1 ## CPC - G06F 12/00: Accessing, addressing or allocating within memory systems or architectures (digital input from, or digital output to record carriers, e.g. to disk storage units, G06F3/06) - G06F 3/0604: {Improving or facilitating administration, e.g. storage management} - G06F 3/0607: {by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device} - G06F 3/0655: {Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices} - G06F 3/0661: {Format or protocol conversion arrangements} - G06F 3/0682: {Tape device} - G06F 3/0686: {Libraries, e.g. tape libraries, jukebox} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract In an embodiment, a method can include sending an I/O request from a mainframe to a virtual tape server. The method can further include reading a non-virtual tape file from the virtual tape server to the mainframe over a virtual tape protocol if the I/O request is a read request. The method can further include writing a non-virtual tape file from the mainframe to the virtual tape server over the virtual tape protocol if the I/O request is a write request. ## Claims ### Claim 1 A method comprising: sending an I/O request from a mainframe to a virtual tape server; and reading data content, stored as a file on the virtual tape server that is not configured in a tape format, from the virtual tape server to the mainframe over a virtual tape protocol if the I/O request is a read request, and writing data content, to be stored as a file on the virtual tape server that is configured in a tape format, from the mainframe to the virtual tape server over the virtual tape protocol if the I/O request is a write request. ### Claim 2 (depends on 1) The method of claim 1, wherein the virtual tape protocol is a Fibre Connection (FICON). ### Claim 3 (depends on 1) The method of claim 1, wherein the I/O request includes an indication of at least one of a direction of transfer, a file name, a file format, a file length, a file owner, and a file permission. ### Claim 4 (depends on 1) The method of claim 1, further comprising enabling configuration, by a user, of the virtual tape server to enable or disable reading or writing the data content from the virtual tape server. ### Claim 5 (depends on 1) The method of claim 1, wherein reading or writing the data content between the mainframe and the virtual tape server using the virtual tape protocols is performed over a non-network interface. ### Claim 6 A system comprising: a request module configured to send an I/O request from a mainframe to a virtual tape server; and a read module configured to read data content, stored as a file on the virtual tape server that is not configured in a tape format, from the virtual tape server to the mainframe over a virtual tape protocol if the I/O request is a read request; and a write module configured to write data content, to be stored as a file on the virtual tape server that is not configured in a tape format, from the mainframe to the virtual tape server over the virtual tape protocol if the I/O request is a write request. ### Claim 7 (depends on 6) The system of claim 6, wherein the virtual tape protocol is a Fibre Connection (FICON). ### Claim 8 (depends on 6) The system of claim 6, wherein the I/O request includes an indication of at least one of a direction of transfer, a file name, a file format, a file length, a file owner, and a file permission. ### Claim 9 (depends on 6) The system of claim 6, further comprising a user interface module configured to enable configuration, by a user, of the virtual tape server to enable or disable reading or writing the data content from the virtual tape server. ### Claim 10 (depends on 6) The system of claim 6, wherein read module and write module are configured to read the data content from or write the non-virtual tape data to, respectively, the virtual tape server using the virtual tape protocols over a non-network interface. ### Claim 11 A method comprising: responsive to an input/output (I/O) request from a mainframe, sending data content, stored as a file on the virtual tape server that is not configured in a tape format, from a virtual tape server to the mainframe over a virtual tape protocol if the I/O request is a read request, and receiving data content, to be stored as a file on the virtual tape server that is not configured in a tape format, from the mainframe to the virtual tape server over the virtual tape protocol if the I/O request is a write request. ### Claim 12 (depends on 11) The method of claim 11, wherein sending the data content from the virtual tape server further includes reading the data content from a non-virtual tape drive on or operatively connected to the virtual tape server. ### Claim 13 (depends on 11) The method of claim 11, wherein receiving the data content from the mainframe further includes writing the received data content to a non-virtual tape drive on or operatively connected to the virtual tape server. ### Claim 14 (depends on 11) The method of claim 11, wherein the virtual tape protocol is a Fibre Connection (FICON). ### Claim 15 (depends on 11) The method of claim 11, wherein the I/O request includes an indication of at least one of a direction of transfer, a file name, a file format, a file length, a file owner, and a file permission. ### Claim 16 (depends on 11) The method of claim 11, further comprising enabling configuration, by a user, of the virtual tape server to enable or disable reading or writing the data content from the virtual tape server. ### Claim 17 (depends on 11) The method of claim 11, wherein reading or writing the data content between the mainframe and the virtual tape server using the virtual tape protocols is performed over a non-network interface. ### Claim 18 A system comprising: a reception module to receive an input/output request from a mainframe; and a transfer module configured to, responsive to the I/O request from the mainframe, send data content, stored as a file on the virtual tape server that is not configured in a tape format, from a virtual tape server to the mainframe over a virtual tape protocol if the I/O request is a read request, and receive data content, to be stored as a file on the virtual tape server that is not configured in a tape format, from the mainframe to the virtual tape server over the virtual tape protocol if the I/O request is a write request. ### Claim 19 (depends on 18) The system of claim 18, wherein the transfer module is further configured to send the data content from the virtual tape server by reading the data content from a non-virtual tape drive on or operatively connected to the virtual tape server. ### Claim 20 (depends on 18) The system of claim 18, wherein the transfer module is further configured to receive the data content from the mainframe by writing the received data content to a non-virtual tape drive on or operatively connected to the virtual tape server. ### Claim 21 (depends on 18) The system of claim 18, wherein the virtual tape protocol is a Fibre Connection (FICON). ### Claim 22 (depends on 18) The system of claim 18, wherein the I/O request includes an indication of at least one of a direction of transfer, a file name, a file format, a file length, a file owner, and a file permission. ### Claim 23 (depends on 18) The system of claim 18, further comprising enabling configuration, by a user, of the virtual tape server to enable or disable reading or writing the data content from the virtual tape server. ### Claim 24 (depends on 18) The system of claim 18, wherein reading or writing the data content between the mainframe and the virtual tape server using the virtual tape protocols is performed over a non-network interface.