|
Not saying you're in error, Dennis, and my memory gets parity checks
frequently, but I remember serving on the System/36 Requirements
committee,
which was pretty much in the same time period as the System/38. Maybe
the
36 folks were just a little bit more aggressive than the damby, pamby
38
crowd. .-)
I do recall that they were Resolutions at some point, just can't swear
to
what the point was.
Jerry C. Adams
IBM i Programmer/Analyst
You give 100% in the first half of the game, and if it isn't enough, in
the
second half you give what's left. - Yogi Berra
--
A&K Wholesale
Murfreesboro, TN
615-867-5070
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dennis
Sent: Monday, April 18, 2011 8:08 AM
To: Midrange Systems Technical Discussion
Subject: RE: Copying and Pasting from MS Word
Ummm - might have to check my history books, but I am pretty certain
that
S/38 and its Resolutions predated AS/400 and its Requirements. :)
"Jerry C. Adams" <midrange@xxxxxxxx> wrote:
Before that they were called "Requirements". We even had softwarerequirements,
running
on a rack mounted AS/400 into which attendees could enter
andthem,
then committees for each project (now defunct) could edit / merge
andimplemented.
then members could vote on them. Chuck Myaard and I used to have to
tear
down the AS/400 in Registration on committee night (usually lasting
past
midnight) and then re-assemble it in Reg before 0800. Chuck was a
wizard
with hardware; I just strung Twinax cables - miles of it!
I imagine IBM eventually balked at the term "Requirements" because it
gave
the impression that the ones voted by the members would be
Notcomplain
always the case.
Jerry C. Adams
IBM i Programmer/Analyst
You got to be careful if you don't know where you're going because you
might
not get there. - Yogi Berra
--
A&K Wholesale
Murfreesboro, TN
615-867-5070
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
iseries@xxxxxxxxxxxx
Sent: Saturday, April 16, 2011 10:36 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Copying and Pasting from MS Word
Dang! I missed that link at first read! Sorry! ("Resolutions" was
the
answer.)
Now where is that needed RECALL button?
Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"A hospital is no place to be sick."
-- movie mogul Sam Goldwyn
These were COMMON User requests to IBM from S/38 days. (What<i>did</i>
they call those things back then??!!??)on
One I liked from the same set, was a request to change library list
between command executions. IBM response: "AVAILABLE. Press ENTER
a command line. Note how the screen blinks."
Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Those who make the worst use of their time are the first to
justof its shortness."from
-- Jean de La Bruyre
Luis--
The command you want was created Once Upon A Time:
INCKBDVTG - Increase Keyboard Voltage. Useful to prevent users
userreplying to messages that say "Contact IT before continuing!"
In the same vein, TRMUSR (*IMMED|*FAMILY) lets you get rid of a
who Just Won't Learn!
The *FAMILY option increases voltage to the monitor until it gives
off a burst of radiation sufficient to sterilize the user.
The *IMMED option increases the voltage even more-- and leaves
afor
pile of ashes on the chair.
Unfortunately, it only works with CRT monitors.
See http://archive.midrange.com/midrange-l/200205/msg01600.html
Iinsert)the entire list of needed commands!
--Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx
At 8:35 AM -0430 4/16/11, Luis Rodriguez wrote:
Robert,
You could define a BEFORE trigger (either for update and/or
and
check and fix the bad data before it gets to the file.
That said, although chopping off fingers seems a little extreme,
shocksalways
thought that it would be nice to have a way to send electric
to
themailing
users thru the keyboard :-)--
IF %USER_ERROR >= n;
SEND_SHOCK();
ENDIF:
Regards,
Luis Rodriguez
IBM Certified Systems Expert - eServer i5 iSeries
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
Sent from my Galaxy tablet phone with with K-9 Mail. Please excuse my
brevity.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.