A: The most frequent reason is that another user’s job has a lock on the student’s record that your job requires in order to continue. If someone else in your office is also working with the same student (or account), or you suspect someone in another office is, ask them to exit the screen they are on and see if your job continues. If it is still held up, submit an Online Help Request and OIT staff will help track down the offender.
The most frequent reason for a “dogging” MBC400 is that someone is running a batch job interactively (i.e. not “jobq”ed). All batch jobs should be submitted to the jobq. No batch jobs should be run interactively. Batch jobs run interactively cause interactive jobs to run very slowly.
Interactive jobs do a single-transaction read or update and go back to waiting on the user, so they spend most of the time waiting on input, and do not consume many system resources. Batch jobs process a number of transactions without requiring user involvement. (Typical batch jobs are reports, labels, and mass maintenances or other programs which do bulk file updates.) The way the 400 manages jobs, interactive jobs get extra resources, so a screen with a person in front of it doesn’t take too long to respond. When batch jobs are run interactively, they also get extra resources. But they never come back to a screen and release those resources–they just keep hogging them.
When debugging a new report or mass maintenance spec you have created, it may take several attempts to get it working correctly, and you may be tempted to run it interactively to speed up the process. The MBC400 user community would prefer you don’t do this. If you must, please change the selection spec so that it only selects one or two students (or one or two accounts), so the time your job interferes with others’ jobs is as short as possible.
In a client server environment, it can be a challenge identifying where between the MBC400 and the networked printer a problem lies. Submit an Online Help Request, and OIT network staff and applications staff will work together to debug your problem and fix it. Printer problems typically occur when a PC upgrade has occurred, or new software of one sort or another has been installed on your PC. If you can identify recent changes made to your PC hardware and software and include that in your email, that will give us a head start.
If you are a remote site user, you may be having difficulty with the network connecting to Mary Baldwin or with VPN. If you cannot yet see the green-on-black MBC400 signon screen, your problem is a network or VPN problem. If your site is using the Software Based VPN Client, make sure you have launched it and logged into MBUNET before attempting to launch your MBC400 session.
Once you can see the green-on-black MBC400 signon screen, have filled in your user and password information, and pressed <ENTER>, and the MBC400 will not let you on, then if you are a brand new MBC400 user, your account may not have been set up yet. Submit an Online Help Request indicating how you are trying to sign on and who your supervisor is. (We need the supervisor’s name to verify authorization and to determine the existing user to model your access security on.)
If you are an existing user, most likely your password has timed out after 90 days of inactivity or you have used an incorrect password three times and your account has been automatically disabled as a security precaution. Submit an Online Help Request and the help desk personnel will re-enable your account for you.