Top Banner
Session 25- 1
41

Session 25-

Jan 11, 2016

Download

Documents

kamea

Session 25-. 1. Session 25. Mainframe Connectivity Session. Introductions. Audience: Those who use a mainframe or midrange platform to send and receive data Evaluations: We appreciate your feedback Questions: Please hold questions till end of presentation. Session Description. - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Session 25-

Session 25- 1

Page 2: Session 25-

Session 25- 2

Session 25

Mainframe Connectivity Session

Page 3: Session 25-

Session 25- 3

Introductions

Audience: Those who use a mainframe or midrange platform to send and receive data

Evaluations: We appreciate your feedback Questions: Please hold questions till end of

presentation

Page 4: Session 25-

Session 25- 4

Session Description

This session reviews Student Financial Assistance (SFA) plans to move the Title IV WAN from a proprietary network to the Internet, and its impact on the user community.

Page 5: Session 25-

Session 25- 5

Today’s Agenda

Comm-Press v4.4

Internet Objectives

Internet Requirements

Current State

Internet Solution

How the Internet Solution Affects You

Page 6: Session 25-

Session 25- 6

Today’s Agenda

Transition Strategy

User Concerns

Further Assistance

Questions

Page 7: Session 25-

Session 25- 7

Comm-Press v4.4 Difference between v3.0.1 & v4.4 Helpful hints for compression and decompression Distribution timeline Minimum platform requirements

Page 8: Session 25-

Session 25- 8

Difference Between v3.0.1 & v4.4?

State-of-the-art data compression techniques to

reduce the size of data files by as much as 95%

Enhanced DECOMP feature to write partial or

corrupt files to DATAXX file

USEREXIT is replaced with SECFILE

Page 9: Session 25-

Session 25- 9

COMPRESS Difference Running v3.0.1: //COMP301 EXEC PGM=COMPRESS, // PARM='UXIT=COMPEXIT,ASCII,CRLF'

Running v4.4: //COMP44 EXEC PGM=COMPRESS, // PARM='ASCII CRLF SECFILE=DD:SECFILE'

Page 10: Session 25-

Session 25-10

COMPRESS Helpful Hints

When executing COMPRESS the parameters of ASCII, CRLF and SECFILE are required

– PARM='ASCII CRLF SECFILE=DD:SECFILE’

ASCII - Causes COMPRESS to translate the data to ASCII or EBCDIC, if necessary, depending on the platform where the data is decompressed

Page 11: Session 25-

Session 25-11

COMPRESS Helpful Hints

CRLF - Causes COMPRESS to convert delimiter characters (for example, line feeds or carriage return/line feed pairs) into record separators

SECFILE - Replaces USEREXIT and causes COMPRESS to recognize header/trailer:

HEADERLITERAL(O*N05) HEADERSTART(1);

TRAILERLITERAL(O*N95) TRAILERSTART(1);

LITERAL(O*N01) LITERALSTART(1);

LITERAL(O*N99) LITERALSTART(1);

Page 12: Session 25-

Session 25-12

COMPRESS Helpful Hints

Using the DD statement COMPLOG, defined as RECL=121,RECFM=FB,will provide additional information regarding the compression of the data

Page 13: Session 25-

Session 25-13

DECOMP Difference Running v3.0.1: //DCOMP301 EXEC PGM=DECOMP

Running v4.4: //DCOMP44 EXEC PGM=COMPRESS, // PARM=’SAFE CRLF UNCOMP SECFILE=DD:SECFILE'

Page 14: Session 25-

Session 25-14

DECOMP Helpful Hints

When executing DECOMP the parameters of SAFE CRLF UNCOMP and SECFILE are required

– PARM=’SAFE CRLF UNCOMP SECFILE=DD:SECFILE’

SAFE - This option causes DECOMP to create a

reject file (DATAXX) containing data that fails

decompression. Only valid data is written to the

output file(s)

Page 15: Session 25-

Session 25-15

DECOMP Helpful Hints CRLF - During decompression, the delimiter

characters that are appropriate for the target platform replace the record separators

UNCOMP - This option signals DECOMP that the input files contain valid uncompressed data in addition to compressed data. DECOMP will copy the uncompressed data to the output files as it decompresses

Page 16: Session 25-

Session 25-16

DECOMP Helpful Hints SECFILE - Replaces USEREXIT and causes

DECOMP to recognize header/trailer:

HEADERLITERAL(O*N05) HEADERSTART(1);

TRAILERLITERAL(O*N95) TRAILERSTART(1);

LITERAL(O*N01) LITERALSTART(1); LITERAL(O*N99) LITERALSTART(1);

Partial files will be written, uncompressed, to the DATAXX file and not the DATAOT file with an invalid return code of 69

Page 17: Session 25-

Session 25-17

Distribution Timeline

Beta conducted during October Production distribution of software during

November:

– CD-ROM includes software and documentation for your platform

– Installation instructions

– Mainframe user guide (includes Comm-Press v4.4 Guide)

– User assistance information

Page 18: Session 25-

Session 25-18

Minimum Platform Requirements

Mainframe: OS/390 1.2

Midrange: AIX 4.1, 4.2, and 4.3, HPUX 10.0,

SunSolaris 2.6, DEC Alpha VMS 7.2, DEC Tru64

4.0, SCO Unix 3.2, and OS/ 400 3.7

PC: Windows 95, 98, 2000 and NT

Page 19: Session 25-

Session 25-19

Internet Objectives

Increase customer satisfaction by providing non-intrusive SFA solutions

Reduce overall cost of delivering student aid

Reduce operating costs through consolidation of operations / systems

Increase schools’ access to SFA databases within Privacy Act constraints and with appropriate security measures

Page 20: Session 25-

Session 25-20

Internet Requirements Move the transmission of Title IV data from the

current proprietary network to the Internet Protect security & privacy of data Reduce costs Increase customer satisfaction Meet and/or exceed performance standards Support multiple platforms

Page 21: Session 25-

Session 25-21

Internet Requirements Support network header/trailer Support FTP, XML, TCP/IP, EDI traffic Support standard FTP ports (20 & 21) Support archive/restore Support audit tracking Support batch/API processes

Single point of administration

Page 22: Session 25-

Session 25-22

Current State

Two store and forward systems:

– Open*Net (non-PC, approximately 150, includes Title IV application systems)

– Enterprise (PC, approximately 7,000)

Redundant expenses and overhead:

– GEIS data center (Open*Net)

– VDC data center (Enterprise)

Page 23: Session 25-

Session 25-23

Current State

Proprietary network (kilo-character charges) Non-COTS solution

Page 24: Session 25-

Session 25-24

Current State

SFA EndU ser(PC )

GEIS VAN

Enterprise

IBM

T itle IVApplication

System s

IB M

SFA End-U ser(m idrange,m ainfram e)

Student(PC )

IB M

O pen*N et

Virtual Data Center

GEIS

Bridge

R em oteAdm in

= Open*Net

= Enterprise

Page 25: Session 25-

Session 25-25

Internet Solution

Consists of one store and forward system Consists of three components Supports mainframe, midrange, and PC

platforms Supports secure TCP/IP-based FTP file transfers

over Internet

Page 26: Session 25-

Session 25-26

Three Components EasyAccess2000 - Client used by SFA end users and

Title IV application systems to send / receive data KeyManager2000 - Administrative system to perform

mailbox management and other administrative duties SecurePortal2000 - Store and forward system which

replaces Open*Net and Enterprise

Page 27: Session 25-

Session 25-27

Proposed State

(*) SFAEnd-U ser

(PC )

Internet(SSL 3.0)

SecurePorta l& Key

M anager

IBM

(*) T itle IVApplication

System s

IBM

(*) SFA End-U ser (m idrange,

m ainfram e)

(*)Student

(PC )

Virtual Data Center

(*) SFA Constituents would use the EasyAccess Client to send/receive data.

Rem oteAdm in

Page 28: Session 25-

Session 25-28

Minimum Platform Requirements

Mainframe: OS/390 1.2

Midrange: AIX 4.1, 4.2, and 4.3, HPUX 10.0,

SunSolaris 2.6, DEC Alpha VMS 7.2, DEC Tru64

4.0, SCO Unix 3.2, and OS/ 400 3.7

PC: Windows 95, 98, 2000 and NT

Page 29: Session 25-

Session 25-29

Network Access Requirements

Required TCP/IP libraries and assumes that the TCP/IP connection is available via a dedicated circuit or dial-up

Page 30: Session 25-

Session 25-30

How the Internet Solution Affects You

Impact Analysis:

Install new software and update existing job

streams Must have Internet connection to send/receive

data

Page 31: Session 25-

Session 25-31

How the Internet Solution Affects You

Benefit Analysis:

Reduced costs (no kilo-character charges) Supports diverse user platforms (PC,

midrange, mainframe) Leverage already in-place Internet connection

Page 32: Session 25-

Session 25-32

How the Internet Solution Affects You

Benefit Analysis:

Non-intrusive Internet solution (no hardware or software costs)

Header/Trailer, Batch number supported Continue to use existing processes with

minimal changes

Page 33: Session 25-

Session 25-33

A Closer Look At “Non-PC” Users

Current ‘RECEIVE’ takes three steps:

1.BPARSER:– Connect– Receive– Disconnect

2.ONVTAM62 (Open*Net Communication)3.Decompress

Page 34: Session 25-

Session 25-34

A Closer Look At “Non-PC” Users

Proposed ‘RECEIVE’ takes one step:

1.PGM=EA2KMVSC, PARM=‘CMDFILE’

– The CMDFILE contains the RECEIVE command-line to be executed

– In one step, the EA2KMVS PGM will:• Connect

• Receive & Decompress

• Disconnect

Page 35: Session 25-

Session 25-35

A Closer Look At “Non-PC” Users

EA2KMVSC is highly robust and supports 92 keywords and commands

Examples:

– SEND

– SENDCLASS

– RECEIVE

– RECEIVECLASS

– FTPPASSWD

Page 36: Session 25-

Session 25-36

A Closer Look At “PC Users”

PC users download and install new version of

EDconnect from SFAdownload.ed.gov

Continue to use EDconnect software to SEND

and RECEIVE data

Page 37: Session 25-

Session 25-37

Transition Strategy

Engage all constituents up-front

Get buy-in from SFA user community early on

Leverage best practices from prior network

migrations

Develop aggressive, yet prudent transition

plans

Page 38: Session 25-

Session 25-38

Transition Strategy

Include “Quick Hit Plan” to move high volume users first

Conversion to Internet will begin 2001

Page 39: Session 25-

Session 25-39

User Concerns What if my platform isn’t supported under the

Internet solution?

How can I plan for the Internet transition?

How can I participate in the Internet beta?

Page 40: Session 25-

Session 25-40

Further Assistance

We appreciate your feedback and comments!

Contact: Title IV WAN Customer Service

Phone: 1-800-615-1189

Email: [email protected]

Page 41: Session 25-

Session 25-41

Questions

?