Scope: All GM-dedicated mainframe complexes in Plano, TX
Effective Date: March 1, 2013
Group Name: HP GSC35 Global Mainframe Operations Account
Affected Locations: AHIPC1N, AHIPC2Y, DNIPC1A, PLIPC1A, PLIPC1B, PLIPC3D, PLIPC4B
Summary: Eliminate usage of SMTP on GM-dedicated complexes for non-GM business functions.
Justification: General Motors (GM) has announced its intent to in-source mainframe operations from HP. The project is currently planned for 2013-14.
The HP Transition team has identified Simple Message Transfer Protocol (SMTP) as a service impacted by the GM Data Center Transition (DCT). GM plans to "lift-and-shift" entire complexes to its new corporate mainframe in Warren, Michigan. Once the transition of a complex is complete, the complex in the current HP-managed environment will be closed down. Any NON-GM SMTP activity routed through that complex will be impacted if not eliminated before the transition occurs.
Benefits to Users: None
Details: Applications that use SMTP for NON-GM purposes on the complexes listed above must change their application to point to their account's mainframe to be assured of uninterrupted service.
No impact and no changes are required if the user or batch application supports a GM business function.
Examples of impacted NON-GM accounts: FISERV, DELPHI, BLUE CROSS/BLUE SHIELD
This is an example of SMTP JCL.
//JS010 EXEC PGM=WAAPDSUT,
// PARM='ABEND'
//SYSUT1 DD DSN=DATA.SET.NAME,
// DISP=(SHR,KEEP,KEEP)
//SYSUT2 DD SYSOUT=A,
// DEST=(PLIPC1A,NETISMTP)
//SYSPRINT DD SYSOUT=*
Primary Contact:
Mark Krantz, HP GSC35 Mainframe Operations Manager
Secondary Contact:
Ted Urbanowicz, HP GSC35 Programme Manager
|
Usercomm - Eliminate Non-GM SMTP Usage from GM complexes