JES(VERIFY/NOVERIFY) in V16

Document ID : KB000113739
Last Modified Date : 13/09/2018
Show Technical Document Details
Question:

The doc says :

VERIFY | NOVERIFY Is ignored at CA Top Secret Release 16 and higher Does this mean that VERIFY is the default ?

In TSSPARM we still have JES(NOVERIFY)

TSS9661I CA TOP SECRET JES STATUS
 JCT(INDEV=0328,ROUTE=0324,NJHDR=0000)
 JES(SSID=JES2,TYPE=JES2,LEVEL=Z/OS 2.1,NOVERIFY)
 JESNODE(*NONE*) NJEUSR(NJE)
 JOBACID(U,8,0) SUBACID(U,8)
Answer:
We had several internal discussion about JES(NOVERIFY).

When TSS r16.0 came GA, JES(NOVERIFY) was no longer supported, but introduced an issue for some customers using JES2 exits.
This being said JES(NOVERIFY) was reestablish with PTF RO88932.
Then we need to add support for IBM maintenance OA53954/OA53955 with PTFs SO04024 and SO04627. 
Then we need to add support for JES_NJE_SECURITY OA49171 NODE CHECKING with PTF SO04936 and finally hyper PTF SO05230 is required to complete support brought by SO04024 and SO04627.

Then today JES(NOVERIFY) is supported, but will only insert USER=user# and NOT the PASSWORD= on the jobcard.

To summarize, you can keep JES(NOVERIFY). The submitting acid being always checked by TSS.