Hi Tom, In 1985, who was running MVT? Regards, David
On 2019-08-22 19:05, Thomas Kern wrote: > Thirty-four years ago I taught my Federal customers (MVT sysprogs) > that there were three things I could not do once I had proper > communications. > > 1) I could not mount tapes > 2) I could not tear paper off the printers > 3) I could not press the Power button > > Now we no longer have mainframe attached tape drives. We no longer > have mainframe attached printers. > And with the improved communications, I CAN power the system up and down. > > Managers want me at a desk in a office so they can feel they have some > power over my work. None of them could do my work if they tried. > > /Tom Kern > On 08/21/2019 17:15, David Spiegel wrote: >> Hi Ron, >> For SysProgs in particular, what is gained by having people "at the >> office"? >> I view this as old school, without justification. >> If project milestones are set properly, the employees will have to work >> consistently to meet them (and not goof off). >> If the managers think that they can see who's working, they are >> mistaken. >> >> I can see where development staff might have to work at the office if >> the environment is highly collaborative. >> (I worked on an online banking project (3 years ago) where this was >> necessary. >> >> Charles: I work at 3 jobs (not all busy at once), all remote. >> >> Regards, >> David >> >> On 2019-08-21 17:02, McCabe, Ron wrote: >>> If this is something that should not have been done on the list I >>> apologize but do have to admit that I would like to see what other >>> companies are allowing in this area. >>> >>> Yes our employer does allow for mainframe sysprogs and developers to >>> work from home. >>> There are restrictions and the main one is who your manager is. Our >>> developers have a nice manager and allows them to work from home 2 >>> days a week, our sysprogs have a different manager and he only >>> allows 1 day per week. >>> No policies have been changed. >>> About 90% of my colleagues work from home. Our developers are also >>> allowed to work 9 80's and 4 10's, sysprogs and admins do not get to >>> as they have to work 5 days a week. >>> >>> Thanks, >>> Ron McCabe >>> Manager of Mainframe/Midrange Systems >>> Mutual of Enumclaw >>> >>> -----Original Message----- >>> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On >>> Behalf Of Charles Mills >>> Sent: Wednesday, August 21, 2019 1:46 PM >>> To: IBM-MAIN@LISTSERV.UA.EDU >>> Subject: Attitude of companies toward mainframers working from home? >>> >>> I am doing a favor for a friend who is writing a blog article on the >>> above subject, with an emphasis on the effect of the shrinking >>> mainframe personnel pool. (This is NOT some disguised headhunter >>> pitch. Reply to the list or to me personally. I will take full >>> responsibility for "sanitizing" your e-mail address and so forth out >>> of what I forward to my friend.) >>> >>> Does your employer allow mainframe sysprogs and developers to work >>> from home? >>> Any particular restrictions or qualifications? >>> Have they changed their policies specifically to address the >>> shrinking mainframe personnel pool? >>> Roughly what percentage of your colleagues work from home? >>> >>> Thanks! >>> >>> Charles >>> >>> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, send >>> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >>> Confidentiality Notice: This e- mail and all attachments may contain >>> CONFIDENTIAL information and are meant solely for the intended >>> recipient. It may contain controlled, privileged, or proprietary >>> information that is protected under applicable law and shall not be >>> disclosed to any unauthorized third party. If you are not the >>> intended recipient, you are hereby notified that any unauthorized >>> review, action, disclosure, distribution, or reproduction of any >>> information contained in this e- mail and any attachments is >>> strictly PROHIBITED. If you received this e- mail in error, please >>> reply to the sender immediately stating that this transmission was >>> misdirected, and delete or destroy all electronic and paper copies >>> of this e-mail and attachments without disclosing the contents. This >>> e- mail does not grant or assign rights of ownership in the >>> proprietary subject matter herein, nor shall it be construed as a >>> joint venture, partnership, teaming agreement, or any other formal >>> business relationship. >>> >>> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >>> . >>> >> >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > . > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
