×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I checked the joblog and determined that "the cure is worse than the disease", so I just put my special environment back. Needing a lower case command line is rare, and I've been living with it forever.
Thanks
-----Original Message-----
From: Rob Berendt [mailto:rob@xxxxxxxxx]
Sent: Tuesday, February 11, 2020 12:19 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: 5250 mixed case command line
I would look for that joblog. Perhaps you have an initial program or menu which is dependent on S/36 environment?
Since you obviously have the authority to do things like CHGUSRPRF then you are probably not set up as a "limited capabilities" user. If so then on the login screen type in
Program/procedure . . . . . . . . qcmd
Menu . . . . . . . . . . . . . . main
With your special environment set to *NONE and the above two values you should no longer have this forced log off.
I have an lpar which starts me out with an Infor LX "menu". If I want to bypass that I just type in QCMD as my initial program.
Then again, if the only issue is that your command line is all uppercase you could just suck it up and accept it.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
midrange.com
