You can indeed remove the line from the VVT file. And, also ERASE HCPBIS
AUXlcl, otherwise soem VMSES/E tools will warn about the difference between
VVT and AUX files.
And, you can run
VMFSIM GETLVL ZVM CP TDATA :PART HCPBIS TXT
to see how VMSES reacts (and which version of HCPBIS will be included in the
CP nuc.
(this VMFSM is something I always issue when getting a fixtest, to check
that what I defined makes indeed the fixtest version gets used. Here's my
GETLVL EXEC
/* This exec is a fastpath to VMFSIM GETLVL
+-----------------------------------------------------------+
| format: | GETLVL fname |
| or: | GETLVL component fname <ftype> |
+-----------------------------------------------------------+
Written by: Kris Buelens 21 Jun 2005*/
parse upper source . . myname mytype . syn .
address command
parse upper arg comp fn ft fm rest . '(' options
if fn='' then do
fn3=left(comp,3)
Select
when fn3='DMS' then parse value 'CMS' comp with comp fn
when fn3='HCP' then parse value 'CP' comp with comp fn
when fn3='AGW' then parse value 'AVS' comp with comp fn
when fn3='GCT' then parse value 'GCS' comp with comp fn
Otherwise nop
end
end
select
when comp='' | fn='' then
call errexit 5,'Missing parms req: comp fn <ft>'
When comp='CP' then ppf='ZVM CP'
When comp='CMS' then ppf='ZVM CMS'
When comp='AVS' then ppf='ZVM AVS'
When comp='GCS' then ppf='ZVM GCS'
Otherwise
call errexit 5, 'Component "'comp'" not defined in' myname mytype
end
if ft='EXEC' then ft='EXC'
else if ft='TEXT' then ft='TXT'
'PIPE COMMAND',
'EXEC VMFSIM GETLVL' ppf 'TDATA :PART' fn ft '|CONS|VAR FILE'
if words(file)=2 then 'LISTFILE' file '* (ISO'
exit rc
ERREXIT: /* general errorexit routine */
parse upper source . . myname mytype . syn .
do i=2 to arg() /* give errormessages (if any) */
say myname':' arg(i)
end
exit arg(1)
2008/12/18 Shimon Lebowitz <[email protected]>
> First, thank you JR.
>
> Luckily I looked it up, and ran it first with the (TEST option.
> It seems that I cannot use this tool, since it wants to
> remove all subsequent mods too.
>
> When I made the mode to BIS to add the exit call,
> I wrote a corresponding mod to my local exit module.
> So if I remove the HCPBIS mod, it will then go and
> delete the next 8 changes I made to POLCMD.
>
> I actually don't mind leaving the code for that exit
> in POLCMD, since I wrote a later update file which
> deleted it. But what I need is some way of telling
> SES that HCPBIS can be used just the way IBM
> gave it to me, without my mod.
>
> Any suggestions?
>
> Thanks,
> Shimon
>
>
> > VMFREM PPF zvm CP MOD modid
> >
> >
> > JR (Steven) Imler
> > CA
> > Senior Sustaining Engineer
> > Tel: +1 703 708 3479
> > [email protected]
> >
> >
> >
>
> --
> ************************************************************************
> Shimon Lebowitz mailto:[email protected]
> VM System Programmer .
> Israel Police National HQ.
> Jerusalem, Israel phone: +972 2 542-9877 fax: 542-9308
> ************************************************************************
>
--
Kris Buelens,
IBM Belgium, VM customer support
