Banyan Vines Session Terminates Early: Difference between revisions
No edit summary |
|||
(2 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
Return to [[The | Return to [[The Software Shelf]] | ||
Last update: 10th February, 1996 | Last update: 10th February, 1996 | ||
Line 7: | Line 7: | ||
== Hardware == | == Hardware == | ||
This so far has | This so far has occurred on Dell's IBM and some Clones. | ||
== Problem == | == Problem == | ||
While trying to login to a Banyan Vines Server an Error occurs COM:104 Which means... | While trying to login to a Banyan Vines Server an Error occurs COM:104 Which means... | ||
COM104 | COM104 - OUT OF HEAP SPACE. | ||
The tasking system within the service could not obtain | The tasking system within the service could not obtain | ||
sufficient memory to perform the request. If this error | sufficient memory to perform the request. If this error | ||
Line 19: | Line 18: | ||
== Procedure == | == Procedure == | ||
Instead of using the command ban.exe command to run the login program. | Instead of using the command ban.exe command to run the login program. Do the following: | ||
Create an OS/2 Session icon and put the program name C:\VINES\BAN.EXE /NL | Create an OS/2 Session icon and put the program name C:\VINES\BAN.EXE /NL | ||
Line 26: | Line 25: | ||
This will load the Banyan Drivers and activate the z:\ drive. | This will load the Banyan Drivers and activate the z:\ drive. | ||
Then Create another OS/2 icon and call it LOGON.CMD. In this file put the | Then Create another OS/2 icon and call it LOGON.CMD. In this file put the following program in it. | ||
following program in it. | |||
<pre> | <pre> | ||
/* This program will clear the environment vars from a OS/2 Session */ | /* This program will clear the environment vars from a OS/2 Session */ | ||
Line 51: | Line 47: | ||
map=sysdrivemap('Z:',REMOTE) | map=sysdrivemap('Z:',REMOTE) | ||
end | end | ||
IF MAP='Z:' THEN | IF MAP='Z:' THEN | ||
DO | DO | ||
SAY "Verifying that LOGIN.EXE exists on the Z:\ drive" | SAY "Verifying that LOGIN.EXE exists on the Z:\ drive" | ||
Line 75: | Line 71: | ||
"EXIT" | "EXIT" | ||
end | end | ||
Otherwise | Otherwise | ||
DO | DO | ||
SAY "NOT ENOUGH MEMORY" | SAY "NOT ENOUGH MEMORY" | ||
Line 86: | Line 82: | ||
== Notes == | == Notes == | ||
What the problem is, is the LOGIN.EXE program is calling the routines necessary to login and | What the problem is, is the LOGIN.EXE program is calling the routines necessary to login and validate you on the system. While doing this, it copies the current environment to the LOCAL HEAP. BAD idea, Anyhow, What this program does and wipe out the environment vars for that OS/2 Session and then RUNs the z:\login.exe program. | ||
It works Great!!!!!! | It works Great!!!!!! | ||
Any questions ??? | Any questions ??? Send a note to jafrank@ibm.net or jfranklin@fdic.gov | ||
''By John Franklin'' | ''By John Franklin'' | ||
Return to [[The | Return to [[The Software Shelf]] | ||
[[Category:The Warp Pharmacy]] | [[Category:The Warp Pharmacy]] |
Latest revision as of 17:14, 22 December 2024
Return to The Software Shelf
Last update: 10th February, 1996
Symptoms
After logging into the Banyan Vines Server, the session is terminated without reading profile.
Hardware
This so far has occurred on Dell's IBM and some Clones.
Problem
While trying to login to a Banyan Vines Server an Error occurs COM:104 Which means...
COM104 - OUT OF HEAP SPACE.
The tasking system within the service could not obtain sufficient memory to perform the request. If this error occurs consistently, there may be a problem with the service.
Procedure
Instead of using the command ban.exe command to run the login program. Do the following:
Create an OS/2 Session icon and put the program name C:\VINES\BAN.EXE /NL Assuming your Vines directory is c:\vines.
This will load the Banyan Drivers and activate the z:\ drive.
Then Create another OS/2 icon and call it LOGON.CMD. In this file put the following program in it.
/* This program will clear the environment vars from a OS/2 Session */ /* Then it will check to see if you have the already executed the ban.exe */ /* program, if so it will reset the environment and run login.exe otherwise */ /* it will run ban.exe with the parameter of /NL for no login then it will */ /* run the same code as above */ call RxFuncAdd 'Sysloadfuncs', 'RexxUtil', 'Sysloadfuncs' call sysloadfuncs Call SysCls say "Enter your Login ID:" pull logid map=sysdrivemap('Z:',REMOTE) if map <>'Z:' THEN do "C:\VINES\BAN.EXE /NL" map=sysdrivemap('Z:',REMOTE) end IF MAP='Z:' THEN DO SAY "Verifying that LOGIN.EXE exists on the Z:\ drive" rc=sysfiletree("Z:\LOGIN.EXE",STUFF.0,F,,) SELECT WHEN rc=0 THEN DO env='OS2ENVIRONMENT' RCV= VALUE('PROMPT','',ENV) RCV= VALUE('PATH','',ENV) RCV= VALUE('DPATH','C:\OS2\SYSTEM',ENV) RCV= VALUE('HELP','',ENV) RCV= VALUE('AUTOSTART','',ENV) RCV= VALUE('BOOKSHELF','',ENV) RCV= VALUE('SOMIR','',ENV) "Z:\LOGIN.EXE" logid "exit" end WHEN RC=1 THEN DO SAY "HEY DUMMY YOU'RE ALREADY LOGGED IN TO THE NETWORK" CALL SysSLEEP 15 "EXIT" end Otherwise DO SAY "NOT ENOUGH MEMORY" CALL SysSLEEP 15 "EXIT" END end /* end select */ END /* end if */
Notes
What the problem is, is the LOGIN.EXE program is calling the routines necessary to login and validate you on the system. While doing this, it copies the current environment to the LOCAL HEAP. BAD idea, Anyhow, What this program does and wipe out the environment vars for that OS/2 Session and then RUNs the z:\login.exe program.
It works Great!!!!!!
Any questions ??? Send a note to jafrank@ibm.net or jfranklin@fdic.gov
By John Franklin
Return to The Software Shelf