MASTER 

COMPUTER GROUP, INC.    27063 Laurel Lane · Olmsted Township, OH 44138 · (800) 526-3744, (888) 526-3744/fax



[Home]   [Software]   [Support / Ideas]   [Consulting]   [Related Links]   [Contact Us]

 

JWEB

Webform replacement for SCOBOL
File Maintenance Autoform and Browser

 

Download and Demo without registration.  Try it FREE for 6 months.   DOWNLOAD

 

JWEB allows you to have a web based interface for your application, often with no programming.

 

How it works.

Typically, applications use a SCOBOL 6530 terminal based screen to accept data from users, send transactions to servers, and display the results.  JWEB replaces the user interface with a web browser based webform.

 

  • Enter the name of an inter–process–message structure that represents data currently sent to your server.  JWEB automatically generates an initial HTML page with a form that has fields for all your data elements.

 

  • Place the generated form into your favorite HTML editor.  Move the fields around and make the page look the way you want.  Add graphics and text as needed.

 

    • Define button properties using our special format in the button name to indicate the action:
    • Transaction Code to be sent
    • Dictionary location describing the message structure
    • Name of the message structure to send
    • Name of the Pathmon process where the server resides
    • One or more reply codes expected.
    • Name of the message structure used in the server reply
    • The HTML webform to display the results

 

  • Save the HTML form as an EDIT file on the Tandem.

 

When a button is clicked, all of the fields in the web form will be mapped to the indicated message structure and sent via TCP/IP and Pathsend to your existing server.  When the server completes the transaction, the fields from the resulting message structure are mapped to the same or a different form for presentation to the user.

 


 

Automatic Webforms for simple file maintenance and reporting.

 

Once the JWEB application in installed, the user enters a URL in the browser and is presented with a web form as shown below:

 

 

Our logo can be replaced by your logo by supplying the graphic.

 

The user fills out the form and clicks the GENERATE button.

 


 

Users can perform complete file maintenance functions.

 

Browsing.

When the user clocks the BROWSE button, a multi–record view is displayed.  Users can indicate which fields should be included on the browse form by checking the checkbox next to the fields desired.

 

 

Users can page through the various records and select any record by clicking the button next to the desired record.  The user will be returned to the original form with the entire selected record displayed and available for maintenance.

 

Users can browse with filtering by placing a check in the 2nd checkbox next to the desired field and filling in a value.  Only records containing the filter values will be displayed when browsing.

 

 


 

The JWEB software includes all the software required to perform automatic form generation for file maintenance of your TMF audited or non–audited key–sequenced files.

 

Stand Alone File Maintenance Applications.

If you don’t like the look of the generated form, the form can be edited in any HTML editor and saved as an EDIT file on the Tandem.  The webform application will still work (minus the Browse function).

 

Other features:

Display any type of Enscribe, Edit, or OSS file.

Convert OSS files to ASCII for display

Display files with non–printable characters suppressed.

Produce a file maintenance webform for any Enscribe key–sequenced file that has a dictionary description.

Use a form to populate any structure and send to any server under any Pathway and display the results, no coding required.

Supports text plus  binary16, 32, and 64–bit field types.

Webforms can be saved as a file and accessed with full functionality intact.

Webforms can be modified in web authoring software for appearance.

Webforms can reference graphics files residing on the Tandem, or anywhere in the network or Internet.

Fields can be protected or removed.  Removed fields are left unchanged on updates.

Data from files or interprocess messages can be displayed on forms as text.

Download binary files to disk.

TCP/IP Data and Logic trace logging available.

Distributed processing.

Supports any number of simultaneous ports.

Webform can be send to any server in any Pathway accessible.

Webform can use any dictionary accessible.

Webform can reference any record layout or message structure.

Redefines are supported.

Multiple nested occurs supported.

User defined transaction codes.

Forms and response structures dependent upon reply code values.

Forms can call other forms, passing linkage and optionally performing initial transactions.

Supports TMF audited files and transactions.

Dynamic content:  Web form elements can be composed of full or partial data values returned from servers.

Checkbox selection from multiple field occurrances.


 

FORMSERV.

FORMSERV is a universal I/O server for performing general I/O operations on key–sequenced files audited or non–audited files.  This is the server that “automatic file maintenance” forms use, but any form an make use of this server.

 

Special field names can be added to a form file that control the operation of the form.  These fields are generally hidden since is it not desirable to see them on the form itself.

 

Examples:

            WX_ADVISORY

            Indicate where advisory text from the FORMSERV server should be displayed.

 

      WX_LINKAGE

            Indicates a message structure of to carry form values between forms.


 

Security.

 

For applications where security is an issue, HTTPS tunneling can be added through open source or third–party products such as XyGate.  This allows for messages that pass between browsers and Tandem servers are encrypted.

 

We also offer a security module with complete security maintenance and reporting to limit or control access to the Tandem from the JWEB application.

 

Sample logon form:

 

 

Sample User Access Maintenance form:

 


 

Sample Audit Log:

 

Security Features:

 

  • User ID expiration.
  • Password expiration.
  • Forced password change.
  • Passwords stored on file are encrypted.
  • Encrypted password hash used in form validation.
  • Inactivity session timeout.
  • Password history reuse limits.
  • Invalid logon limits.
  • Freeze user ID option.
  • Users can only access the initial form defined for their user ID, and other forms called by the initial form or subsequent forms.
  • Graphics directory can be defined for open access to all users for displaying logos, icons, etc.
  • User logon audit logging.
  • User maintenance audit logging.
  • Clients can supply their own password encryption/decryption routines.
  • Clients can supply their own password strength requirement routines.
  • Access to links, files, and other forms can be limited to only work when the source is a form accessed via the security form.


 

Browsing Files.

 

 

vs.

 


 

Scroll back and forth through entire file with search capability, no wrapping.

 

vs.

 

24 x 80 single screen view with wrapping.


 

Scroll back and forth through large files with search capability.

 

vs.

 

24 x 80 single screen view

 

 

vs.

 

 

The below working form with report viewer was built in 5 minutes without coding using only Word for Windows as an HTML editor.

 

 

vs.

 

The Scobol screen and report viewer took over 60 hours to build.


 

JWEB  view with control characters changed to periods

 

vs.

 

FUP COPY with control characters corrupting the 6530 display

 

Automatically generated form with browse and filter options.

 

vs.

 

15 Page Enable


 

Sample HTML generated by AUTOFORM

 

<html><head><title>$TEST01.TP04ATS.AHLALF Maintenance</title></head><body><b> <font face="Lucida Console" size="4"></font><form method="POST"

 action="/?FORM:$TEST01.TP04ATS.AHLALF/AHLALF-REC/$TEST01.TP00DICT"

 

<b>File: <b><input type="text" name="WX_DATAFILE" size="40" maxlength="35" value="$TEST01.TP04ATS.AHLALF">

<b>Rec: <b><input type="text" name="WX_RECORD" size="35" maxlength="30" value="AHLALF-REC">

<b>Dict: <b><input type="text" name="WX_DICT" size="31" maxlength="26" value="$TEST01.TP00DICT">

<input type="submit" value="Generate" name="BUTTON_FORM2">

<input type="hidden" name="WX_REF" value="http://192.168.2.231:1234/?FORM:$TEST01.TP04ATS.AHLALF/AHLALF-REC/$TEST01.TP00DICT">

<input type="hidden" name="WX_LOGON-HASH" value="                                                                ">

<table border=0 cellspacing=0 cellpadding=0><tr><td valign=top>

<input type="submit"

 value="Read

Exact "

 name="BUTTON_READ"

 style="font-size: 9pt; font-family: Arial; font-weight: bold"

&nbsp;

&nbsp;

 

<input type="submit"

 value="Read

Approx"

 name="BUTTON_READAPPROX"

 style="font-size: 9pt; font-family: Arial; font-weight: bold"

&nbsp;

&nbsp;

<input type="submit"

 value="Read

Prev  "

 name="BUTTON_READPREV"

 style="font-size: 9pt; font-family: Arial; font-weight: bold"

...

...

<br>

<input type="checkbox" name="CB_0004" CHECKED><input type="checkbox" name="FL_0004">

  ____LOGON-ID-1

&nbsp;&nbsp;

 

<input type="text"

 name="DF_LOGON-ID-1"

 size="0008"

 maxlength="0008"

 style="font-size: 12pt; font-family: Lucida Console; color:blue; font-weight: bold"

 

<br>

<input type="checkbox" name="CB_0005" CHECKED><input type="checkbox" name="FL_0005">

  ____LOGON-ID-2

&nbsp;&nbsp;

 

<input type="text"

 name="DF_LOGON-ID-2"

 size="0008"

 maxlength="0008"

 style="font-size: 12pt; font-family: Lucida Console; color:blue; font-weight: bold"

...

...

<br>

<b><font face="Arial" size="1" color="blue">Sel/Filter</font></form><b><font face="Arial" size="1" color="red">end-of-form</font>

</body></html>


 

Sample HTML for Custom Button

 

<input type="submit"

 value="Read

Exact "

 name="BT_00010:

  RECORD LOGON-TRANS:

  SERVER LOGON:"

 style="font-size: 9pt; font-family: Arial; font-weight: bold"

 

The above HTML code produces a two–line button that looks like:

 

 

It sends:

  transaction code 10

  using message structure LOGON–TRANS

  to server class LOGON

 

It has other HTML for default values for the form name and dictionary location:

  <input type="hidden" 

  name="WX_DICT" size="31" maxlength="26"

  value="JWEBDICT">

 

  <input type="hidden"

  name="WX_FORMNAME" size="31" maxlength="26"

  value="JWEBFORM.LOGONM">

 

It defaults to using the Pathway under which JWEB is running, since no Pathmon process is specified.

 

 

 

Button Name format used to define click actions:

BT_xxxxx:

[DICT <vol.sub>:]

[RECORD <structure name>:]

[PATHMON <pathmon process name>:]     Defaults to creator of HTTP process

[SERVER <server class>:]              If missing, no send is performed

[REPLY <reply structure name>:]

[REPLY_xxxxx,<reply structure name>,FORM <form name>:]

[FORM <form name>:]

[–Sxxxxx]                             Field selection from multiple occurrences

 

Values between square brackets are options.


 

URL formats:

HTTP://<ip-address>:port>/<\node.$vol.subvol.filename>                Displays file or HTML document/form.

HTTP://<ip-address>:port>/<OSS Filename>                     Displays file or HTML document/form.

HTTP://<ip-address>:port>/<OSS Filename>@                    Displays file, CR/LF added to end of each line

HTTP://<ip-address>:port>/<\node.$vol.subvol.filename>@              Displays file, CR/LF added to end of each line

HTTP://<ip-address>:port>/<\node.$vol.subvol.filename>.              Non–displayable characters converted to periods.

HTTP://<ip-address>:port>/?FORM <\node.$vol.subvol.filename>/<record-name>/<dict-location>

                                                                                                                    Auto generates file maintenance / browse form.