Starting NPM with a SESSCOLL requires a manual start to get data at times
Coding an APPL statement in FNMINIT or a SESSAPPL command in FNMSTRT member sometimes requires a manually start collection to get data.
Resolving the problem
NPM allows the use of either an APPL statement in FNMINIT or a SESSAPPL command in FNMSTRT to define local applications for collection. It also allows the use of the SESSCOLL command to start collection during initialization. However, you may find that collection isn't always started if "DYNAMIC=" isn't set to yes as one of the parameters within the SESSCOLL command. (It defaults to 'NO') What this does is tell NPM, and VTAM that the application may not be active when NPM is started and VTAM should allow NPM to collect it even if that is the case. In this case, VTAM will notify NPM through a unique return code that the resource isn't active but is valid. NPM logic will then defer collection until VTAM notifies NPM through the NPM interface that the resource can be collected at which time NPM will start collection. This won't happen, however, unless you code DYNAMIC=YES on the SESSCOLL command.