Possible Problems With PAMS 6

[Old-Navy]

Okay.. just got this one in the company e mail.  

All,



GCSS-AF is still trying to figure out why PAMS is so slow lately and one of the contributing factors they found is not logging out properly.  Please pass on to all users that they should click "Logoff" instead of the 'X' (exit) on the top-right of the screen.  Apparently hitting the X does not close the session to the database and ties up resources until the database automatically closes the connection after 15 minutes of inactivity.   Our programmers are looking into making the 'X' do the same thing as Logoff; while this is not the main cause of the sluggish performance it should help improve performance.    





DANNY L.VESSELLS, MSgt, USAF

Hq SSG/ILMO

201 East Moore Dr

Maxwell AFB, Gunter Annex AL

DSN 596-1159

Comm (334) 416-1159

[MIRCS]

Poor Danny.......I know he is going crazy with this right now.

[browndav]

Well...  If that is what is causing the snail like performance of PAMS 6.0 were all doomed.  With a very small percentage of the bases that are going to be using this system online how will it perform when all of the bases are up and running.  Even is the LOGOUT button error is the problem with all bases online there are going to be so many users on at the same time that I have a weird FEELING that the servers are going to get so bogged down they eventually burn up....  explode....  and destroy half the base.

[Old-Navy]

HERE'S ANOTHER ONE....  Explains why Pope and Kirtland are taking actions on my stuff.  

We recently discovered this bug in the system; the normal process is to look up previous MDC actions to make sure you don't take J when you've already taken an F.  What's happening is that other labs use the same JCN sequence numbers and the program looks up the wrong JCN - in the other words it finds a matching JCN but for another Lab. This problem just didn't surface in the last nine months testing with 2 labs.

The work-around for now is to go ahead enter whatever code makes it happy, and then go into the Time Correction screen to the correct the code.

It's actually already been fixed in our development system and should be installing the software release on the live system this week.  

Danny