Thanks. I'll try that next time I'm mucking there. I'm in the process of reipling all the systems now to verify that the dynamic changes I made today stick after an IPL.
Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get&[email protected] ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, June 9, 2019 12:29 PM, Mike Schwab <[email protected]> wrote: > https://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieae200/ieae200140.htm > > The following syntax rules apply to COUPLExx: > > Use columns 1 through 71. Do not use columns 72 - 80 for data; these > columns are ignored. > At least one delimiter (space or comma) is required between a > statement and keyword. Delimiters are not required between keywords. > Use at least one delimiter to separate multiple keyword values within > parentheses. > Comments may appear in columns 1-71 and must begin with "/" and end with "/". > > https://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieae200/ieae200141.htm > > [COUPLE SYSPLEX(sysplex-name)] > [CFRMPOL(CFRMPOLNAME)] > [CFRMOWNEDCFPROMPT(NO|YES)] > [CFRMTAKEOVERCF(NO|PROMPT)] > [PCOUPLE(primary-dsname[,primary-volume]) ] > [ACOUPLE(alternate-dsname[,alternate-volume]) ] > [INTERVAL(time-interval) ] > [OPNOTIFY(time-interval) ] > [CLEANUP(cleanup-interval) ] > [MAXMSG(default maxmsg) ] > [RETRY(default retry-limit) ] > [CLASSLEN(default class-length) ] > [CTRACE(parmlib-member) ] > [VMCPUIDTOLERATION(NO|YES) ] > [FUNCTIONS {ENABLE(function[,function …]) } > {DISABLE(function[,function …])} ] > [CLASSDEF ] > [ CLASS(class-name) ] > [ [CLASSLEN(class-length) ] ] > [ [MAXMSG(max-messages) ] ] > [ [GROUP(group-name[,group-name]...)] ] > [PATHIN ] > [ {DEVICE(device-number[,device-number]...) } ] > [ {STRNAME(strname[,strname]...) } ] > [ [MAXMSG(max-messages)] ] > [ [RETRY(retry-limit) ] ] > [PATHOUT ] > [ {DEVICE(device-number[,device-number]...) } ] > [ {STRNAME(strname[,strname]...) } ] > [ [MAXMSG(max-messages)] ] > [ [RETRY(retry-limit) ] ] > [ [CLASS(class-name)] ] > [LOCALMSG ] > [ MAXMSG(max-messages) ] > [ [CLASS(class-name)] ] > [DATA ] > [ TYPE(name[,name]...) ] > [ PCOUPLE(primary-dsname[,primary-volume]) ] > [ [ACOUPLE(alternate-dsname[,alternate-volume])]] > [SYNCASYNC ] > [ SIMPLEX(nnnnn|DEFAULT) ] > [ DUPLEX(nnnnn|DEFAULT) ] > [ LOCKDUPLEX(nnnnn|DEFAULT) ] > [ LOCKSIMPLEX(nnnnn|DEFAULT) ] > > In column 2 do a Keyword and the first subkeyword with (value) or > (value1,value2,etc) on one line. > Indented, do additional subkeyword with value(s) on additional line. > Repeat for additional Keywords. > > On Sun, Jun 9, 2019 at 3:05 PM Mark Jacobs > [email protected] wrote: > > > I'm enabling several optional functions in my COUPLExx parmlib member, and > > they all don't fit on one line. During IPL it's complaining if I have > > multiple FUNCTIONS ENABLE statements in the member, and I can't get the > > syntax right for it to read the options across multiple lines. > > What's the magic, SETXCF FUNCTIONS command in COMMNDxx? > > Mark Jacobs > > Sent from ProtonMail, Swiss-based encrypted email. > > GPG Public Key - > > https://api.protonmail.ch/pks/lookup?op=get&[email protected] > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > -- > > Mike A Schwab, Springfield IL USA > Where do Forest Rangers go to get away from it all? > > -------------------------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
