The dictname needed in OLQ to use SS=IDMSNWKA is the one for which you ran IDMSDIRL during Configuration. Normally this is SYSDIRL.
SIG SS=IDMSNWKA DICT SYSDIRL DBNAME SYSDICT
OLQ 100021 00 Ready to retrieve data from subschema IDMSNWKA
OLQ 100022 00 Schema: IDMSNTWK Version: 1
OLQ 100023 00 Database name: SYSDICT
OLQ 100025 00 Dictionary name: SYSDIRL
If you have a dictionary called SYSDIRL try that. It has to be the dict for which the IDMSDIRL job ran during configuration. IDMSDIRL adds the network Schema and Subschema source which OLQ needs.
The IDMSNWKA loadmod is in CAGJLOAD and will be loaded from CDMSLIB but OLQ needs the source as well.
If you verify that the IDMSNTWK/IDMSNWKA schema/SS source is in the dict you are connecting to, then the other possibility is that the dictionary has SECURITY FOR OLQ IS ON in the dictionary options, and the USER def in that dict for the user attempting this in OLQ does not have the ACCESS TO SUBSCHEMA IDMSNWKA clause.
ACCESS TO SUBSCHEMA subschema-name.
For example:
If you have already verified that the subschema source is indeed in the dictionary but you still get the error message:
OLQ 094012 04 The subschema-name subschema cannot be found in the DEFAULT dictionary
Then most likely it is because OLQ Security is ON and your USER statement in IDD does not include the ACCESS TO SUBSCHEMA subschema-name clause.
To determine, go into IDD and signon to the dictionary where the subschema source resides.
Issue the command:
DISPLAY USER user-id.
Do you see the clause: ACCESS TO SUBSCHEMA subschema-name ?
If not you can modify the USER statement to include the ACCESS TO SUBSCHEMA
clause as follows:
MOD USER user-id
ACCESS TO SUBSCHEMA subschema-name OF SCHEMA schema-name VERSION IS version-number.