I'm the Service Owner for a z13 Mainframe supporting hundreds of critical banking applications. This year we're redesigning our service model. [u]Service Orientation, Cloud Commoditization and �Tri-Modal� IT initiatives are on the horizon.
Mainframes in my Financial Institution have been quietly and efficiently running in the background for years. It�s time to �evangelize� their relevance.
I was wondering what others are doing to describe what services the Mainframe offers � Imagine the services being offered in a Service Catalogue � comments and suggestions welcome:
1. Application Hosting
2. Batch Management
3. Service Continuity *( Including Data Replication)
4. Inter-Application connectivity
5. Data Services *(data stores aren�t changing, they�re being used as data sources for new apps hosted elsewhere)
6. Specialized Services (leveraging new functionality/environments, �specialty� engines)
7. Testing Services
8. Developments Services
when somebody is willing to use such porte-manteau(Mot-valise) constructs like the ones in the starting topic
the technical content is pretty irrelevant
as in ... leveraging new functionality/environments, ‘specialty’ engines
so just ask somebody well versed in marketingspeak and forget about the reality of Your services
here is a foggy sentence generator which might help in writing the flyers
Code:
#! /usr/bin/rexx
Parse Arg times
/* List of LEADINS, all of which mean nothing but buy time */
leadin.1 = "In particular,"
leadin.2 = "On the other hand,"
leadin.3 = "However,"
leadin.4 = "Similarly,"
leadin.5 = "As a resultant implication,"
leadin.6 = "In this regard,"
leadin.7 = "Based on integral subsystem considerations,"
leadin.8 = "For example,"
leadin.9 = "Thus,"
leadin.10 = "In respect to specific goals,"
leadin.11 = "Interestingly enough,"
leadin.12 = "Without going into the technical details,"
leadin.13 = "Of course,"
leadin.14 = "To approach true user-friendliness,"
leadin.15 = "In theory,"
leadin.16 = "It is assumed that"
leadin.17 = "Conversely,"
leadin.18 = "We can see, in retrospect,"
leadin.19 = "It is further assumed that"
leadin.20 = "Further,"
leadin.21 = "In summary,"
leadin.22 = "It should be noted that"
leadin.23 = "To further describe and annotate,"
leadin.24 = "Specifically,"
leadin.0 = 24
/* List of SUBJECT clauses chosen for no redeeming value whatsoever */
subject.1 = "a large portion of interface coordination communication"
subject.2 = "a constant flow of effective communication"
subject.3 = "the characterization of specific criteria"
subject.4 = "initiation of critical subsystem development"
subject.5 = "the fully integrated test program"
subject.6 = "the product configuration baseline"
subject.7 = "any associated supporting element"
subject.8 = "the incorporation of additional mission constraints"
subject.9 = "the independent functional principle"
subject.10 = "the interrelation of system and/or subsystem technologies"
subject.11 = "the product assurance architecture"
subject.0 = 11
/* List of VERB clauses chosen for auto-recursive obfuscation */
verb.1 = "must utilize and be functionally interwoven with"
verb.2 = "maximizes the probability of project success, yet minimizes cost and time required for"
verb.3 = "adds explicit performance limits to"
verb.4 = "necessitates that urgent consideration be applied to"
verb.5 = "requires considerable systems analysis and trade-off studies to arrive at"
verb.6 = "is further compounded when taking into account"
verb.7 = "presents extremely interesting challenges to"
verb.8 = "recognizes other systems' importance and the necessity for"
verb.9 = "affects a significant implementation of"
verb.10 = "adds overriding performance constraints to"
verb.11 = "mandates staff-meeting-level attention to"
verb.12 = "is functionally equivalent and parallel to"
verb.0 = 12
/* List of OBJECT clauses selected for profound meaninglessness */
object.1 = "the most recent level of hardware. "
object.2 = "the anticipated fourth-generation equipment. "
object.3 = "the subsystem compatibility testing. "
object.4 = "the structural design, based on system engineering concepts. "
object.5 = "the preliminary qualification limit. "
object.6 = "the evolution of specifications over a given time period. "
object.7 = "the philosophy of commonality and standardization. "
object.8 = "the greater fight-worthiness concept. "
object.9 = "any discrete configuration mode. "
object.10 = "the management-by-contention principle. "
object.11 = "the total system rationale. "
object.12 = "possible bidirectional logical relationship approaches. "
object.13 = "the postulated use of dialog management technology. "
object.14 = "the overall negative profitability. "
object.0 = 14
If times = '?' Then Do
say "foggy.rex"
say " FOGGY is an interactive productivity tool designed to assist"
say " in the composition of monthly reports, project plans, memos to"
say " management and so forth. If entered without parameters,"
say " FOGGY generates as output a high-fog-index sentence suitable for"
say " befuddling even the most determined seeker-after-content. If you"
say " need vast amounts of FOGGY for really serious tush-covering, enter"
say " the number of sentences needed as a parameter. For example,"
say " entering 'FOGGY 5' outputs half a screen of heat-treated, battle-"
say " hard, industrial-strength slop, well suited to choking hogs and"
say " assurance planners. "
say ""
say " REMEMBER:"
say " FOGGY can be a terrible weapon -- never abuse it."
Exit
End
Do Until outstuff = ''
k = Lastpos(' ',outstuff,Min(linesize,Length(outstuff)))
Say Strip(Left(outstuff,k))
outstuff = Strip(Substr(outstuff,k+1),'L')
End
