# US 2012/0254467 A1 · Mainframe Web Client

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0254467 A1
- Document ID: US20120254467A1
- Status: Published application
- Kind: A1
- Application number: 13/079,539
- Filed: 2011-04-04
- Published: 2012-10-04
- Earliest claimed: 2011-04-04
- Assignees: International Business Machines Corporation
- Inventors: Michael P. Kasper; Ulrich Kurz; Gary S. Puchkoff; Bertold Reddemann; Peter D. Van Dyke
- Web page: https://patentgrep.com/patent/US20120254467A1

## CPC

- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method includes receiving a message in a JavaScript object notation (JSON) format from a first processor, converting the message from the JSON format into a hypertext markup language (HTML) format, and presenting the content of the message in the HTML format to a user on a display.

## Claims

### Claim 1

A method including:
receiving a message in a JavaScript object notation (JSON) format from a first processor;
converting the message from the JSON format into a hypertext markup language (HTML) format; and
presenting the content of the message in the HTML format to a user on a display.

### Claim 2 (depends on 1)

The method of claim 1, wherein the converting the message from the JSON format into the HTML format includes:
identifying a key word of the message in the JSON format;
creating an HTML element associated with the key word; and
filling the HTML element with corresponding data from the JSON format.

### Claim 3 (depends on 1)

The method of claim 1, wherein the message includes a screen ID.

### Claim 4 (depends on 3)

The method of claim 3, wherein the method includes:
determining whether the screen ID of the message matches a screen ID associated with a first portion of the display; and
presenting the content of the message in the HTML format in the first portion of the display responsive to determining that the screen ID of the message matches a screen ID associated with a first portion of the display to the user.

### Claim 5 (depends on 3)

The method of claim 3, wherein the method includes:
determining whether the screen ID of the message matches a screen ID associated with a portion of the display; and
generating a new portion of the display responsive to determining that the screen ID of the message does not match a screen ID associated with a first portion of the display;
presenting the content of the message in the HTML format in the new portion of the display to the user.

### Claim 6 (depends on 1)

The method of claim 1, wherein the converting the message from JSON format into HTML format is performed by a web client application on a second processor.

### Claim 7 (depends on 1)

The method of claim 1, wherein the first processor is a mainframe processor.

### Claim 8 (depends on 1)

The method of claim 1, wherein the message is received from a servlet application.

### Claim 9 (depends on 1)

The method of claim 1, wherein the message is sent from a time sharing option (TSO) address space of the first processor.

### Claim 10 (depends on 1)

The method of claim 1, wherein the message is sent from an interactive system productivity facility (ISPF) session.

### Claim 11 (depends on 1)

An article of manufacture tangibly embodying computer readable instructions which, when implemented, cause a computer to carry out the steps of a method according to claim 1.

### Claim 12

A system including:
a display; and
a first processor communicatively connected to the display, the first processor operative to receive a message in a JavaScript object notation (JSON) format from a second processor, convert the message from the JSON format into a hypertext markup language (HTML) format, and present the content of the message in the HTML format to a user on the display.

### Claim 13 (depends on 12)

The system of claim 12, wherein the converting the message from the JSON format into the HTML format includes:
identifying a key word of the message in the JSON format;
creating an HTML element associated with the key word; and
filling the HTML element with corresponding data from the JSON format.

### Claim 14 (depends on 12)

The system of claim 12, wherein the message includes a screen ID.

### Claim 15 (depends on 12)

The system of claim 12, wherein the first processor is operative to determine whether the screen ID of the message matches a screen ID associated with a first portion of the display; and present the content of the message in the HTML format in the first portion of the display responsive to determining that the screen ID of the message matches a screen ID associated with a first portion of the display to the user.

### Claim 16 (depends on 12)

The system of claim 12, wherein the first processor is operative to determine whether the screen ID of the message matches a screen ID associated with a portion of the display, and generate a new portion of the display responsive to determining that the screen ID of the message does not match a screen ID associated with a first portion of the display, present the content of the message in the HTML format in the new portion of the display to the user.

### Claim 17 (depends on 12)

The system of claim 12, wherein the converting the message from JSON format into HTML format is performed by a web client application on the first processor.

### Claim 18 (depends on 12)

The system of claim 12, wherein the second processor is a mainframe processor.

### Claim 19 (depends on 12)

The system of claim 12, wherein the message is received from a servlet application.

### Claim 20 (depends on 12)

The system of claim 12, wherein the message is sent from a time sharing option (TSO) address space of the first processor.

### Claim 21 (depends on 12)

The system of claim 12, wherein the message is sent from an interactive system productivity facility (ISPF) session.

### Claim 22

A method including:
receiving an input from a user on a first processor;
converting the input from a hypertext markup language (HTML) format to a JavaScript object notation (JSON) format message; and
sending the JSON message to a second processor.

### Claim 23 (depends on 22)

The method of claim 22, wherein the converting the input from the HTML format into the JSON format includes:
adding a screen identifier and panel name to the JSON message;
identifying a type of HTML response in the input;
creating a JSON element associated with the type of HTML response; and
filling the JSON element with corresponding data from the input.

### Claim 24 (depends on 22)

An article of manufacture tangibly embodying computer readable instructions which, when implemented, cause a computer to carry out the steps of a method according to claim 22.

### Claim 25

A system including:
a display; and
a first processor communicatively connected to the display, the first processor operative to receive an input from a user on a first processor, convert the input from a hypertext markup language (HTML) format to a JavaScript object notation (JSON) format message, and send the JSON message to a second processor.
