|
(Posted on the WDSC list, but no response there) Greetings! I have had CL prompting fail several times from the Code/400 editor. I am using a 5250 emulation session (PCOMM V5.6 build 20020814) and a STRCODE server session. I initiate the edit of a CLLE source member from WRKOBJPDM with the following command: /* Evoke Code/400 in Edit Mode */ CALL PGM(QDEVTOOLS/EVFCFDBK) PARM('37' 'Y' 'JIM' '<LOCAL> CODEEDIT "<>&L/&F(&N)"') The editor presents the source to me as normal. When I prompt a CL command the editor uses the 5250 screen, but I don't see the prompt information. The 5250 session hangs, and I never see that server session again (until I reboot). I have to kill the Communication Daemon, All 5250 jobs, the interactive session on the AS/400 (excuse me - iSeries 400), hold my nose, and give a pint of blood. iSeries - V5R2 - Latest CUMM Package WDSc Code editor V4: I have loaded a service pack, I believe it is the latest (I used to know how to get the SP Info, but I've slept since then!) Win2K Service pack 3 with up-to-date security fixes and drivers This problem seems to happen every time I try and prompt, and I have not tried since the last time it failed. (Trying to get this email out before other priorities push it out of what's left of my mind) Is this happening to others?? Do I get to debug a new problem??? As a side issue, the Communication Daemon will still not end when asked about 50 % of the time. I say quit(exit?) and it goes away, then pops right back up. Thanks for letting me rant! ---------------------------------------------------------- Jim Essinger Senior Programmer/Analyst Student Loan Fund of Idaho PO Box 730 Fruitland, ID 83619 208-452-4058 esinger@fmtc.com ------------------------------------------------------------
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.