/******************************************************************************
 * Copyright (c) ETSI 2017.
 *
 * This file is subject to copyrights owned by ETSI. Non-exclusive permission
 * is hereby granted, free of charge, to copy, reproduce and amend this file
 * under the following conditions: It is provided "as is", without warranty of any
 * kind, expressed or implied.
 * 
 * ETSI shall never be liable for any claim, damages, or other liability arising
 * from its use or inability of use.This permission does not apply to any documentation
 * associated with this file for which ETSI keeps all rights reserved. The present
 * copyright notice shall be included in all copies of whole or part of this
 * file and shall not imply any sub-license right.
 *
 * Modified by: Adrien Kirjak
 *
 ** @version  0.0.1
 ** @purpose  1:16.1.2, Ensure that the IUT recognizes predefined functions and correctly evaluates them (as specified by Annex C)
 ** @verdict  pass reject
 ***************************************************/

/* The following requirements are tested:
 *In addition to the general error causes in clause 16.1.2, error causes are:
 * inpar is a template of a character string type and contains a matching mechanism other than AnyElement or
AnyElementsOrNone; */

module NegSem_160102_predefined_functions_036 {
	
	type component GeneralComp {	
	}
	
	testcase TC_NegSem_160102_predefined_functions_036 () runs on GeneralComp {
		
		const universal charstring m_Ref:="abc?def?";
		
		var template universal charstring Mytemp := pattern "{m_Ref}\q{0,0,1,113}";
		var universal charstring v_i;

	 	v_i:=substr(Mytemp,1,2);		//error: non allowed matching mechanism


	}

	control{

		execute(TC_NegSem_160102_predefined_functions_036());

	}

}
