|
Me as well have a short menory with lot's of parity checks. A year ago we converted an old S/36 to a AS/400 m170. I've never worked on the S/36 a know almost nothing about them but I remember that we could not configure more C/A devices then there were devices configured in the *M36 object. You configure them using chgm36 (or is this also a parity check?) Regards // Stefan Tageson +>----------------------------------------------------------------------<+ tel: +46 40 693 3500 fax: +46 40 693 3600 mobile: +46 708 51 3543 e-mail stefan.tageson@notes.sema.se +>---------------------------------------------------------------------<+ DAsmussen@aol .com To: midrange-l@midrange.com cc: (bcc: Stefan Tageson/MMX/Sema Group/SE) 1999-09-03 Subject: M36 Limiting Virtual Devices 08:28 Please respond to MIDRANGE-L Hello Folks! As most of you know, I used to know a lot about S/36E issues. I've now forgotten most of that and never knew _anything_ about the /36 virtual machine. I haven't been involved in the decision process at all, so please bear with me. I have a client that is switching to the AS/400, but they still have an Advanced 36 running their old DMAS accounting software. Said client is rolling out Client Access desktops in a formerly "green screen" environment in preparation for the AS/400 rollover, and I suggested that they establish an icon for the "M36" AS/400 and use the TFRM36 command when they needed to access the old DMAS application. This worked _great_ until the fifth PC was rolled out, and the TFRM36 command fell over with a "Maximum Devices" error and returned to the AS/400 main menu. I've checked the AS/400 system values as well as the M36 configuration and can find no reason for this error. Anybody have any ideas? TIA, Dean Asmussen Enterprise Systems Consulting, Inc. Fuquay-Varina, NC USA E-mail: DAsmussen@aol.com "We know what a person thinks not when he tells us what he thinks, but by his actions." -- Isaac Bashevis Singer +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.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.