The Emulation Session object for the active screen...useful in many calls, and setup as a proxy object for the FVAPISession object. The available properties for emSess are as follows:
fvApi.emSess.screenName -- if recognition is active will contain the active Screen Name recognized after the last screen update by the host
fvApi.emSess.rows -- active Rows in the connected Session's screen
fvApi.emSess.cols -- active Columns in the connected Sessions's screen
fvApi.emSess.GetScnRows -- same as fvApi.GetScnRows
fvApi.emSess.fnSaveChanges -- async function that can be awaited: will save any user changes made in the active 3270 or 5250 screen.
