however, it seems as if this system does expect SYS2.LINKLIB there
It does. But the fact that it isn't there yet isn't a show stopper.
The reason VS1 expects to find SYS2.LINKLIB is that the 'SYS1.PARMLIB(LNKLST00)' member is telling VS1 initialization to look for it:
SYS1.LINKLIB,SYS2.LINKLIB
The sample generating-system/g10-parmlib.jcl job, which builds PARMLIB members, adds the LNKLST00 member along with several others. Because SYS2.LINKLIB hasn't been created yet, VS1 initialization doesn't find it, and issues the message. After you've run the job to create SYS2.LINKLIB, it will exist and VS1 initialization will subsequently find it, and the message will no longer be issued. You won't need it until then anyway. I suppose I could have created SYS2.LINKLIB before adding the LNKLST00 member, but it seemed more straightforward to do it this way. Maybe it would be appropriate to document the warning messages that will be issued at this point which can be ignored.
--
